1s autopkgtest [20:23:29]: starting date and time: 2025-02-15 20:23:29+0000 1s autopkgtest [20:23:29]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 1s autopkgtest [20:23:29]: host juju-7f2275-prod-proposed-migration-environment-2; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.9wfo50h3/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:glibc,src:iproute2,src:php-twig,src:postgresql-17,src:postgresql-common,src:roundcube --apt-upgrade libfprint --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 '--env=ADT_TEST_TRIGGERS=glibc/2.41-1ubuntu1 iproute2/6.13.0-1ubuntu1 php-twig/3.19.0-1 postgresql-17/17.3-2 postgresql-common/273 roundcube/1.6.10+dfsg-1' -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor builder-cpu2-ram4-disk20 --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-2@bos03-11.secgroup --name adt-plucky-amd64-libfprint-20250215-202328-juju-7f2275-prod-proposed-migration-environment-2-0ce0d275-9c56-48fa-b4c2-08e2d512ac02 --image adt/ubuntu-plucky-amd64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-2 --net-id=net_prod-proposed-migration-amd64 -e TERM=linux -e ''"'"'http_proxy=http://squid.internal:3128'"'"'' -e ''"'"'https_proxy=http://squid.internal:3128'"'"'' -e ''"'"'no_proxy=127.0.0.1,127.0.1.1,login.ubuntu.com,localhost,localdomain,novalocal,internal,archive.ubuntu.com,ports.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,changelogs.ubuntu.com,keyserver.ubuntu.com,launchpadlibrarian.net,launchpadcontent.net,launchpad.net,10.24.0.0/24,keystone.ps5.canonical.com,objectstorage.prodstack5.canonical.com,radosgw.ps5.canonical.com'"'"'' --mirror=http://ftpmaster.internal/ubuntu/ 62s autopkgtest [20:24:30]: testbed dpkg architecture: amd64 62s autopkgtest [20:24:30]: testbed apt version: 2.9.28 63s autopkgtest [20:24:31]: @@@@@@@@@@@@@@@@@@@@ test bed setup 63s autopkgtest [20:24:31]: testbed release detected to be: None 65s autopkgtest [20:24:32]: updating testbed package index (apt update) 65s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB] 65s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 65s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 65s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 65s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [820 kB] 66s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B] 66s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.1 kB] 66s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [62.8 kB] 66s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 Packages [82.9 kB] 66s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/main i386 Packages [65.0 kB] 66s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/restricted i386 Packages [2412 B] 66s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/restricted amd64 Packages [7984 B] 66s Get:13 http://ftpmaster.internal/ubuntu plucky-proposed/universe amd64 Packages [844 kB] 66s Get:14 http://ftpmaster.internal/ubuntu plucky-proposed/universe i386 Packages [303 kB] 66s Get:15 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse i386 Packages [3520 B] 66s Get:16 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse amd64 Packages [10.3 kB] 66s Fetched 2329 kB in 1s (2406 kB/s) 67s Reading package lists... 68s Reading package lists... 68s Building dependency tree... 68s Reading state information... 68s Calculating upgrade... 68s The following packages will be upgraded: 68s libtasn1-6 69s 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 69s Need to get 51.2 kB of archives. 69s After this operation, 22.5 kB of additional disk space will be used. 69s Get:1 http://ftpmaster.internal/ubuntu plucky/main amd64 libtasn1-6 amd64 4.20.0-2 [51.2 kB] 69s Fetched 51.2 kB in 1s (73.7 kB/s) 69s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 108914 files and directories currently installed.) 69s Preparing to unpack .../libtasn1-6_4.20.0-2_amd64.deb ... 69s Unpacking libtasn1-6:amd64 (4.20.0-2) over (4.19.0-3build1) ... 69s Setting up libtasn1-6:amd64 (4.20.0-2) ... 69s Processing triggers for libc-bin (2.40-4ubuntu1) ... 69s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. 70s autopkgtest [20:24:38]: upgrading testbed (apt dist-upgrade and autopurge) 70s Reading package lists... 70s Building dependency tree... 70s Reading state information... 70s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 71s Starting 2 pkgProblemResolver with broken count: 0 71s Done 71s Entering ResolveByKeep 71s 71s The following packages will be upgraded: 71s iproute2 libc-bin libc-dev-bin libc6 libc6-dev locales 72s 6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 72s Need to get 11.8 MB of archives. 72s After this operation, 746 kB of additional disk space will be used. 72s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 libc-dev-bin amd64 2.41-1ubuntu1 [24.7 kB] 72s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 libc6-dev amd64 2.41-1ubuntu1 [2182 kB] 72s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 locales all 2.41-1ubuntu1 [4246 kB] 72s Get:4 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 libc6 amd64 2.41-1ubuntu1 [3327 kB] 72s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 libc-bin amd64 2.41-1ubuntu1 [701 kB] 72s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main amd64 iproute2 amd64 6.13.0-1ubuntu1 [1277 kB] 73s Preconfiguring packages ... 73s Fetched 11.8 MB in 1s (9878 kB/s) 73s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 108914 files and directories currently installed.) 73s Preparing to unpack .../libc-dev-bin_2.41-1ubuntu1_amd64.deb ... 73s Unpacking libc-dev-bin (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 73s Preparing to unpack .../libc6-dev_2.41-1ubuntu1_amd64.deb ... 73s Unpacking libc6-dev:amd64 (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 73s Preparing to unpack .../locales_2.41-1ubuntu1_all.deb ... 73s Unpacking locales (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 73s Preparing to unpack .../libc6_2.41-1ubuntu1_amd64.deb ... 73s Checking for services that may need to be restarted... 73s Checking init scripts... 73s Checking for services that may need to be restarted... 73s Checking init scripts... 73s Stopping some services possibly affected by the upgrade (will be restarted later): 73s cron: stopping...done. 73s 73s Unpacking libc6:amd64 (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 74s Setting up libc6:amd64 (2.41-1ubuntu1) ... 74s Checking for services that may need to be restarted... 74s Checking init scripts... 74s Restarting services possibly affected by the upgrade: 74s cron: restarting...done. 74s 74s Services restarted successfully. 74s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 108915 files and directories currently installed.) 74s Preparing to unpack .../libc-bin_2.41-1ubuntu1_amd64.deb ... 74s Unpacking libc-bin (2.41-1ubuntu1) over (2.40-4ubuntu1) ... 74s Setting up libc-bin (2.41-1ubuntu1) ... 74s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 108915 files and directories currently installed.) 74s Preparing to unpack .../iproute2_6.13.0-1ubuntu1_amd64.deb ... 74s Unpacking iproute2 (6.13.0-1ubuntu1) over (6.10.0-2ubuntu1) ... 74s Setting up iproute2 (6.13.0-1ubuntu1) ... 74s Setting up locales (2.41-1ubuntu1) ... 74s Installing new version of config file /etc/locale.alias ... 75s Generating locales (this might take a while)... 76s en_US.UTF-8... done 76s Generation complete. 76s Setting up libc-dev-bin (2.41-1ubuntu1) ... 76s Setting up libc6-dev:amd64 (2.41-1ubuntu1) ... 76s Processing triggers for man-db (2.13.0-1) ... 77s Processing triggers for systemd (257.2-3ubuntu1) ... 78s Reading package lists... 79s Building dependency tree... 79s Reading state information... 79s Starting pkgProblemResolver with broken count: 0 79s Starting 2 pkgProblemResolver with broken count: 0 79s Done 80s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 84s autopkgtest [20:24:52]: testbed running kernel: Linux 6.12.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 4 16:02:16 UTC 2025 85s autopkgtest [20:24:53]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 92s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (dsc) [2928 B] 92s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (tar) [9278 kB] 92s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.8+tod1-0ubuntu1 (diff) [17.5 kB] 92s gpgv: Signature made Tue Sep 3 05:15:30 2024 UTC 92s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 92s gpgv: Can't check signature: No public key 92s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.8+tod1-0ubuntu1.dsc: no acceptable signature found 94s autopkgtest [20:25:02]: testing package libfprint version 1:1.94.8+tod1-0ubuntu1 95s autopkgtest [20:25:03]: build not needed 101s autopkgtest [20:25:09]: test installed-tests: preparing testbed 102s Reading package lists... 102s Building dependency tree... 102s Reading state information... 102s Starting pkgProblemResolver with broken count: 0 102s Starting 2 pkgProblemResolver with broken count: 0 102s Done 102s The following NEW packages will be installed: 102s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 102s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 102s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libgusb2 102s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 102s python3-cairo umockdev 103s 0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded. 103s Need to get 9877 kB of archives. 103s After this operation, 34.6 MB of additional disk space will be used. 103s Get:1 http://ftpmaster.internal/ubuntu plucky/main amd64 fonts-dejavu-mono all 2.37-8 [502 kB] 103s Get:2 http://ftpmaster.internal/ubuntu plucky/main amd64 fonts-dejavu-core all 2.37-8 [835 kB] 103s Get:3 http://ftpmaster.internal/ubuntu plucky/main amd64 fontconfig-config amd64 2.15.0-1.1ubuntu2 [37.3 kB] 103s Get:4 http://ftpmaster.internal/ubuntu plucky/main amd64 gir1.2-json-1.0 amd64 1.10.6+ds-1 [10.0 kB] 103s Get:5 http://ftpmaster.internal/ubuntu plucky/main amd64 libgusb2 amd64 0.4.9-1 [38.6 kB] 103s Get:6 http://ftpmaster.internal/ubuntu plucky/main amd64 gir1.2-gusb-1.0 amd64 0.4.9-1 [7454 B] 103s Get:7 http://ftpmaster.internal/ubuntu plucky/main amd64 libpixman-1-0 amd64 0.44.0-3 [427 kB] 103s Get:8 http://ftpmaster.internal/ubuntu plucky/main amd64 libfprint-2-tod1 amd64 1:1.94.8+tod1-0ubuntu1 [64.6 kB] 103s Get:9 http://ftpmaster.internal/ubuntu plucky/main amd64 libfprint-2-2 amd64 1:1.94.8+tod1-0ubuntu1 [269 kB] 103s Get:10 http://ftpmaster.internal/ubuntu plucky/main amd64 gir1.2-fprint-2.0 amd64 1:1.94.8+tod1-0ubuntu1 [7178 B] 103s Get:11 http://ftpmaster.internal/ubuntu plucky/universe amd64 gnome-desktop-testing amd64 2021.1-4 [16.8 kB] 103s Get:12 http://ftpmaster.internal/ubuntu plucky/main amd64 libfontconfig1 amd64 2.15.0-1.1ubuntu2 [139 kB] 103s Get:13 http://ftpmaster.internal/ubuntu plucky/main amd64 libxcb-render0 amd64 1.17.0-2 [16.2 kB] 103s Get:14 http://ftpmaster.internal/ubuntu plucky/main amd64 libxcb-shm0 amd64 1.17.0-2 [5758 B] 103s Get:15 http://ftpmaster.internal/ubuntu plucky/main amd64 libxrender1 amd64 1:0.9.10-1.1build1 [19.0 kB] 103s Get:16 http://ftpmaster.internal/ubuntu plucky/main amd64 libcairo2 amd64 1.18.2-2 [569 kB] 103s Get:17 http://ftpmaster.internal/ubuntu plucky/main amd64 python3-cairo amd64 1.26.1-2build1 [143 kB] 103s Get:18 http://ftpmaster.internal/ubuntu plucky/universe amd64 libumockdev0 amd64 0.19.1-3 [76.3 kB] 103s Get:19 http://ftpmaster.internal/ubuntu plucky/universe amd64 umockdev amd64 0.19.1-3 [76.5 kB] 103s Get:20 http://ftpmaster.internal/ubuntu plucky/universe amd64 libfprint-2-tests amd64 1:1.94.8+tod1-0ubuntu1 [6618 kB] 104s Fetched 9877 kB in 1s (8636 kB/s) 104s Selecting previously unselected package fonts-dejavu-mono. 104s (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 108916 files and directories currently installed.) 104s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ... 104s Unpacking fonts-dejavu-mono (2.37-8) ... 104s Selecting previously unselected package fonts-dejavu-core. 104s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ... 104s Unpacking fonts-dejavu-core (2.37-8) ... 104s Selecting previously unselected package fontconfig-config. 104s Preparing to unpack .../02-fontconfig-config_2.15.0-1.1ubuntu2_amd64.deb ... 104s Unpacking fontconfig-config (2.15.0-1.1ubuntu2) ... 104s Selecting previously unselected package gir1.2-json-1.0:amd64. 104s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_amd64.deb ... 104s Unpacking gir1.2-json-1.0:amd64 (1.10.6+ds-1) ... 104s Selecting previously unselected package libgusb2:amd64. 104s Preparing to unpack .../04-libgusb2_0.4.9-1_amd64.deb ... 104s Unpacking libgusb2:amd64 (0.4.9-1) ... 104s Selecting previously unselected package gir1.2-gusb-1.0:amd64. 104s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_amd64.deb ... 104s Unpacking gir1.2-gusb-1.0:amd64 (0.4.9-1) ... 104s Selecting previously unselected package libpixman-1-0:amd64. 104s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_amd64.deb ... 104s Unpacking libpixman-1-0:amd64 (0.44.0-3) ... 104s Selecting previously unselected package libfprint-2-tod1:amd64. 104s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.8+tod1-0ubuntu1_amd64.deb ... 104s Unpacking libfprint-2-tod1:amd64 (1:1.94.8+tod1-0ubuntu1) ... 104s Selecting previously unselected package libfprint-2-2. 104s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.8+tod1-0ubuntu1_amd64.deb ... 104s Unpacking libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 104s Selecting previously unselected package gir1.2-fprint-2.0:amd64. 104s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.8+tod1-0ubuntu1_amd64.deb ... 104s Unpacking gir1.2-fprint-2.0:amd64 (1:1.94.8+tod1-0ubuntu1) ... 104s Selecting previously unselected package gnome-desktop-testing. 104s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_amd64.deb ... 104s Unpacking gnome-desktop-testing (2021.1-4) ... 104s Selecting previously unselected package libfontconfig1:amd64. 104s Preparing to unpack .../11-libfontconfig1_2.15.0-1.1ubuntu2_amd64.deb ... 104s Unpacking libfontconfig1:amd64 (2.15.0-1.1ubuntu2) ... 104s Selecting previously unselected package libxcb-render0:amd64. 104s Preparing to unpack .../12-libxcb-render0_1.17.0-2_amd64.deb ... 104s Unpacking libxcb-render0:amd64 (1.17.0-2) ... 104s Selecting previously unselected package libxcb-shm0:amd64. 104s Preparing to unpack .../13-libxcb-shm0_1.17.0-2_amd64.deb ... 104s Unpacking libxcb-shm0:amd64 (1.17.0-2) ... 104s Selecting previously unselected package libxrender1:amd64. 104s Preparing to unpack .../14-libxrender1_1%3a0.9.10-1.1build1_amd64.deb ... 104s Unpacking libxrender1:amd64 (1:0.9.10-1.1build1) ... 104s Selecting previously unselected package libcairo2:amd64. 104s Preparing to unpack .../15-libcairo2_1.18.2-2_amd64.deb ... 104s Unpacking libcairo2:amd64 (1.18.2-2) ... 105s Selecting previously unselected package python3-cairo. 105s Preparing to unpack .../16-python3-cairo_1.26.1-2build1_amd64.deb ... 105s Unpacking python3-cairo (1.26.1-2build1) ... 105s Selecting previously unselected package libumockdev0:amd64. 105s Preparing to unpack .../17-libumockdev0_0.19.1-3_amd64.deb ... 105s Unpacking libumockdev0:amd64 (0.19.1-3) ... 105s Selecting previously unselected package umockdev. 105s Preparing to unpack .../18-umockdev_0.19.1-3_amd64.deb ... 105s Unpacking umockdev (0.19.1-3) ... 105s Selecting previously unselected package libfprint-2-tests. 105s Preparing to unpack .../19-libfprint-2-tests_1%3a1.94.8+tod1-0ubuntu1_amd64.deb ... 105s Unpacking libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 105s Setting up gnome-desktop-testing (2021.1-4) ... 105s Setting up libpixman-1-0:amd64 (0.44.0-3) ... 105s Setting up libxrender1:amd64 (1:0.9.10-1.1build1) ... 105s Setting up libxcb-render0:amd64 (1.17.0-2) ... 105s Setting up libgusb2:amd64 (0.4.9-1) ... 105s Setting up libfprint-2-tod1:amd64 (1:1.94.8+tod1-0ubuntu1) ... 105s Setting up libxcb-shm0:amd64 (1.17.0-2) ... 105s Setting up fonts-dejavu-mono (2.37-8) ... 105s Setting up fonts-dejavu-core (2.37-8) ... 105s Setting up libumockdev0:amd64 (0.19.1-3) ... 105s Setting up gir1.2-json-1.0:amd64 (1.10.6+ds-1) ... 105s Setting up libfprint-2-2 (1:1.94.8+tod1-0ubuntu1) ... 115s Setting up umockdev (0.19.1-3) ... 115s Setting up fontconfig-config (2.15.0-1.1ubuntu2) ... 115s Setting up gir1.2-gusb-1.0:amd64 (0.4.9-1) ... 115s Setting up libfontconfig1:amd64 (2.15.0-1.1ubuntu2) ... 115s Setting up gir1.2-fprint-2.0:amd64 (1:1.94.8+tod1-0ubuntu1) ... 115s Setting up libcairo2:amd64 (1.18.2-2) ... 116s Setting up python3-cairo (1.26.1-2build1) ... 116s Setting up libfprint-2-tests (1:1.94.8+tod1-0ubuntu1) ... 116s Processing triggers for man-db (2.13.0-1) ... 116s Processing triggers for udev (257.2-3ubuntu1) ... 116s Processing triggers for libc-bin (2.41-1ubuntu1) ... 118s autopkgtest [20:25:26]: test installed-tests: gnome-desktop-testing-runner libfprint-2 118s autopkgtest [20:25:26]: test installed-tests: [----------------------- 118s Running test: libfprint-2/driver-elanmoc.test 118s ** (umockdev-run:3681): DEBUG: 20:25:26.562: umockdev.vala:127: Created udev test bed /tmp/umockdev.D9HB22 118s ** (umockdev-run:3681): DEBUG: 20:25:26.562: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 118s ** (umockdev-run:3681): DEBUG: 20:25:26.563: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 118s ** (umockdev-run:3681): DEBUG: 20:25:26.566: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.D9HB22/dev/bus/usb/001/003 118s ** (umockdev-run:3681): DEBUG: 20:25:26.566: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 118s ** (umockdev-run:3681): DEBUG: 20:25:26.567: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 118s ** (umockdev-run:3681): DEBUG: 20:25:26.570: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.D9HB22/dev/bus/usb/001/001 118s ** (umockdev-run:3681): DEBUG: 20:25:26.570: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 118s ** (umockdev-run:3681): DEBUG: 20:25:26.570: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 118s (process:3685): libfprint-context-DEBUG: 20:25:26.658: Initializing FpContext (libfprint version 1.94.8+tod1) 118s (process:3685): libfprint-tod-DEBUG: 20:25:26.659: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.660: 86456429: ../libfprint/drivers/elanmoc/elanmoc.c:1151 118s (process:3685): libfprint-context-DEBUG: 20:25:26.661: No driver found for USB device 1D6B:0002 118s (process:3685): libfprint-device-DEBUG: 20:25:26.661: Device reported probe completion 118s (process:3685): libfprint-device-DEBUG: 20:25:26.661: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.661: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.662: [elanmoc] DEV_INIT_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.662: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.662: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.663: [elanmoc] DEV_INIT_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.663: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.663: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.663: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.664: [elanmoc] DEV_INIT_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.664: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.664: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.664: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.665: elanmoc FW Version 8004 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.665: [elanmoc] DEV_INIT_STATES entering state 3 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.665: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.665: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.665: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.666: elanmoc last_read DIM 0x57(87) 0x6B(107) 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.666: [elanmoc] DEV_INIT_STATES entering state 4 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.666: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.666: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.666: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.667: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.667: [elanmoc] DEV_INIT_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.667: Device reported open completion 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.667: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.667: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.667: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.667: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.667: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.667: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.668: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.668: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.668: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.668: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.668: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.669: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.669: ##### Re-Enrollment Case! ##### 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.669: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.669: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.669: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.670: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.670: Device reported enroll progress, reported 1 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.670: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.670: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.670: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.670: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.671: Device reported enroll progress, reported 2 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.671: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.671: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.671: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.671: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.672: Device reported enroll progress, reported 3 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.672: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.672: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.672: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.672: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.673: Device reported enroll progress, reported 4 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.673: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.673: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.673: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.673: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.674: Device reported enroll progress, reported 5 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.674: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.674: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.674: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.674: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.674: Device reported enroll progress, reported 6 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.674: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.674: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.675: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.675: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.675: Device reported enroll progress, reported 7 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.675: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.675: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.676: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.676: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.676: Device reported enroll progress, reported 7 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.676: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.676: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.676: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.677: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.677: Device reported enroll progress, reported 8 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.677: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.677: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.677: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.678: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.678: Device reported enroll progress, reported 8 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.678: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.678: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.678: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.678: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.679: Device reported enroll progress, reported 9 of 9 have been completed 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.679: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.679: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.679: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.679: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.680: elanmoc_commit_cb success 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.680: Enrollment was successful! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.680: Device reported enroll completion 118s (process:3685): libfprint-device-DEBUG: 20:25:26.680: Print for finger FP_FINGER_UNKNOWN enrolled 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.680: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.680: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.680: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.680: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.680: [elanmoc] MOC_LIST_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.680: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.680: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.681: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.681: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.681: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.681: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.681: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.682: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.682: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.682: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.682: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.683: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.683: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.683: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.683: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.684: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.684: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.684: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.684: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.684: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.684: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.685: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.685: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.685: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.685: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.686: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.686: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.686: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.686: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.686: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.687: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.687: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.687: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.687: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.687: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.688: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.688: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.688: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.688: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.689: [elanmoc] MOC_LIST_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.689: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.689: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.689: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.689: Device reported listing completion 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.689: [elanmoc] MOC_LIST_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.689: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.689: Completing action FPI_DEVICE_ACTION_LIST in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.689: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.690: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.690: [elanmoc] IDENTIFY_NUM_STATES entering state 0 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.690: elanmoc elan_identify_run_state 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.690: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.690: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.690: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.691: [elanmoc] IDENTIFY_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.691: elanmoc elan_identify_run_state 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.691: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.691: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.691: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.691: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.692: Verify was successful! for user: 0 mesg_code: 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.692: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.692: [elanmoc] IDENTIFY_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.692: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.692: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.692: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 118s (process:3685): libfprint-device-DEBUG: 20:25:26.693: Device reported verify result 118s (process:3685): libfprint-device-DEBUG: 20:25:26.693: Device reported verify completion 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.693: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.693: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.693: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.693: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.693: [elanmoc] IDENTIFY_NUM_STATES entering state 0 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.693: elanmoc elan_identify_run_state 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.693: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.693: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.693: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.694: [elanmoc] IDENTIFY_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.694: elanmoc elan_identify_run_state 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.694: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.694: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.694: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.694: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.695: Verify was successful! for user: 0 mesg_code: 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.695: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.695: [elanmoc] IDENTIFY_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.695: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.695: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.695: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 118s (process:3685): libfprint-device-DEBUG: 20:25:26.695: Device reported identify result 118s (process:3685): libfprint-device-DEBUG: 20:25:26.695: Device reported identify completion 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.695: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.695: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.695: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.696: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.696: [elanmoc] DELETE_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.696: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.696: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-device-DEBUG: 20:25:26.697: Device reported deletion completion 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.697: [elanmoc] DELETE_NUM_STATES completed successfully 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.697: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.697: Completing action FPI_DEVICE_ACTION_DELETE in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.697: Not updating temperature model, device can run continuously! 118s (process:3685): libfprint-elanmoc-DEBUG: 20:25:26.697: Elanmoc dev_exit 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.697: [elanmoc] DEV_EXIT_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.697: [elanmoc] FP_CMD_NUM_STATES entering state 0 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.697: [elanmoc] FP_CMD_NUM_STATES entering state 1 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.697: [elanmoc] DEV_EXIT_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.697: Device reported close completion 118s (process:3685): libfprint-SSM-DEBUG: 20:25:26.697: [elanmoc] FP_CMD_NUM_STATES completed successfully 118s (process:3685): libfprint-device-DEBUG: 20:25:26.697: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s (process:3685): libfprint-device-DEBUG: 20:25:26.697: Not updating temperature model, device can run continuously! 118s enrolling 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 1, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 2, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 3, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 4, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 5, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 6, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 7, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 8, None, None, None) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 118s finger status: 118s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x766039421fc0 (FpiDeviceElanmoc at 0x2d5b0620)>, 9, None, None, None) 118s enroll done 118s listing 118s listing done 118s verifying 118s verify done 118s async identifying 118s indentification_done: 118s deleting 118s delete done 118s ** (umockdev-run:3681): DEBUG: 20:25:26.710: umockdev.vala:154: Removing test bed /tmp/umockdev.D9HB22 118s (umockdev-run:3681): GLib-DEBUG: 20:25:26.715: unsetenv() is not thread-safe and should not be used after threads are created 118s PASS: libfprint-2/driver-elanmoc.test 118s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.3.test 118s (process:3691): libfprint-context-DEBUG: 20:25:26.728: Initializing FpContext (libfprint version 1.94.8+tod1) 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Found TOD entry point symbol 0x785fa5b7f987, GType is 98557756879680 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Initializing features for driver ssm_test_dev_tod_v1+1.90.3 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Found TOD entry point symbol 0x785fa5b7953b, GType is 98557756889488 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s (process:3691): libfprint-tod-DEBUG: 20:25:26.729: Initializing features for driver fake_test_dev_tod_v1+1.90.3 118s (process:3691): libfprint-context-DEBUG: 20:25:26.730: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s (process:3691): libfprint-context-DEBUG: 20:25:26.730: created 118s (process:3691): libfprint-device-DEBUG: 20:25:26.730: Device reported probe completion 118s (process:3691): libfprint-device-DEBUG: 20:25:26.730: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s (process:3691): libfprint-device-DEBUG: 20:25:26.730: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:3691): GLib-DEBUG: 20:25:26.730: setenv()/putenv() are not thread-safe and should not be used after threads are created 118s TAP version 14 118s # random seed: R02S7d5417015bfc241cf284608ac39d1f1f 118s 1..97 118s # Start of driver tests 118s ok 1 /driver/get_driver 118s ok 2 /driver/get_device_id 118s ok 3 /driver/get_name 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 4 /driver/is_open 118s ok 5 /driver/get_nr_enroll_stages 118s ok 6 /driver/set_nr_enroll_stages 118s ok 7 /driver/supports_identify 118s ok 8 /driver/supports_capture 118s ok 9 /driver/has_storage 118s ok 10 /driver/do_not_support_identify 118s ok 11 /driver/do_not_support_capture 118s ok 12 /driver/has_not_storage 118s ok 13 /driver/get_usb_device 118s ok 14 /driver/get_virtual_env 118s ok 15 /driver/get_driver_data 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 16 /driver/initial_features 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 17 /driver/probe 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 18 /driver/open 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 19 /driver/close 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 20 /driver/enroll 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 21 /driver/verify 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify result 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 22 /driver/identify 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported capture completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 23 /driver/capture 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported listing completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 24 /driver/list 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported deletion completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 25 /driver/delete 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 26 /driver/clear_storage # SKIP Feature not supported by TODv1 versions before 1.92.0 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 118s # libfprint-device-DEBUG: Device reported deletion completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 27 /driver/cancel 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 28 /driver/critical # SKIP Feature not supported by TODv1 versions before 1.94.0 118s ok 29 /driver/get_current_action 118s ok 30 /driver/timeout 118s ok 31 /driver/error_types 118s ok 32 /driver/retry_error_types 118s # Start of get_scan_type tests 118s ok 33 /driver/get_scan_type/press 118s ok 34 /driver/get_scan_type/swipe 118s # End of get_scan_type tests 118s # Start of set_scan_type tests 118s ok 35 /driver/set_scan_type/press 118s ok 36 /driver/set_scan_type/swipe 118s # End of set_scan_type tests 118s # Start of finger_status tests 118s ok 37 /driver/finger_status/inactive 118s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 118s ok 38 /driver/finger_status/waiting 118s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 118s ok 39 /driver/finger_status/present 118s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 118s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 118s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 118s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 118s ok 40 /driver/finger_status/changes 118s # End of finger_status tests 118s # Start of features tests 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 41 /driver/features/probe_updates # SKIP Feature not supported by TODv1 versions before 1.92.0 118s # End of features tests 118s # Start of initial_features tests 118s ok 42 /driver/initial_features/none 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 43 /driver/initial_features/no_capture 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 44 /driver/initial_features/no_verify 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 45 /driver/initial_features/no_identify 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 46 /driver/initial_features/no_storage 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 47 /driver/initial_features/no_list 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 48 /driver/initial_features/no_delete 118s ok 49 /driver/initial_features/no_clear 118s # End of initial_features tests 118s # Start of probe tests 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 50 /driver/probe/error 118s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 51 /driver/probe/action_error 118s # End of probe tests 118s # Start of open tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 52 /driver/open/error 118s # End of open tests 118s # Start of close tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 53 /driver/close/error 118s # End of close tests 118s # Start of enroll tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 54 /driver/enroll/error 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported enroll progress, reported 317834605 of 79266209 have been completed 118s # libfprint-device-DEBUG: Device reported enroll progress, reported 1252003822 of 79266209 have been completed 118s # libfprint-device-DEBUG: Device reported enroll progress, reported 1349740291 of 79266209 have been completed 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 55 /driver/enroll/progress 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 56 /driver/enroll/update_nbis 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 57 /driver/enroll/update_nbis_wrong_device 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 58 /driver/enroll/update_nbis_wrong_driver 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 59 /driver/enroll/update_nbis_missing_feature 118s # Start of error tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 60 /driver/enroll/error/no_print 118s # End of error tests 118s # End of enroll tests 118s # Start of verify tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 61 /driver/verify/fail 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 62 /driver/verify/retry 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 63 /driver/verify/error 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 64 /driver/verify/not_supported 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 65 /driver/verify/report_no_cb 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 66 /driver/verify/not_reported 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported verify result 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 67 /driver/verify/complete_retry 118s # End of verify tests 118s # Start of identify tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify result 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 118s ok 68 /driver/identify/fail 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify result 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 118s ok 69 /driver/identify/retry 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 70 /driver/identify/error 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 71 /driver/identify/not_reported 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify result 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify result 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported identify result 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 72 /driver/identify/complete_retry 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported identify result 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 73 /driver/identify/report_no_cb 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 74 /driver/identify/suspend_continues # SKIP Feature not supported by TODv1 versions before 1.94.0 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 75 /driver/identify/suspend_succeeds # SKIP Feature not supported by TODv1 versions before 1.94.0 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 76 /driver/identify/suspend_busy_error # SKIP Feature not supported by TODv1 versions before 1.94.0 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 77 /driver/identify/suspend_while_idle # SKIP Feature not supported by TODv1 versions before 1.94.0 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 78 /driver/identify/warmup_cooldown # SKIP Feature not supported by TODv1 versions before 1.94.0 118s # End of identify tests 118s # Start of capture tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 79 /driver/capture/not_supported 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported capture completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 80 /driver/capture/error 118s # End of capture tests 118s # Start of list tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported listing completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 81 /driver/list/error 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 82 /driver/list/no_storage 118s # End of list tests 118s # Start of delete tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported deletion completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 83 /driver/delete/error 118s # End of delete tests 118s # Start of clear_storage tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 84 /driver/clear_storage/error # SKIP Feature not supported by TODv1 versions before 1.92.0 118s # End of clear_storage tests 118s # Start of cancel tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported deletion completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 85 /driver/cancel/fail 118s # End of cancel tests 118s # Start of get_current_action tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 86 /driver/get_current_action/open 118s # End of get_current_action tests 118s # Start of get_cancellable tests 118s ok 87 /driver/get_cancellable/error 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 88 /driver/get_cancellable/open 118s # Start of open tests 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 89 /driver/get_cancellable/open/internal 118s # End of open tests 118s # End of get_cancellable tests 118s # Start of action_is_cancelled tests 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 90 /driver/action_is_cancelled/open # SKIP Feature not supported by TODv1 versions before 1.94.0 118s ok 91 /driver/action_is_cancelled/error 118s # Start of open tests 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s ok 92 /driver/action_is_cancelled/open/internal # SKIP Feature not supported by TODv1 versions before 1.94.0 118s # End of open tests 118s # End of action_is_cancelled tests 118s # Start of complete_action tests 118s # Start of all tests 118s ok 93 /driver/complete_action/all/error 118s # End of all tests 118s # End of complete_action tests 118s # Start of action_error tests 118s ok 94 /driver/action_error/error 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 118s # libfprint-device-DEBUG: Device reported capture completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 118s # libfprint-device-DEBUG: Device reported listing completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 118s # libfprint-device-DEBUG: Device reported deletion completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 95 /driver/action_error/all 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported enroll completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported verify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported identify completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported capture completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported listing completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Device reported deletion completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.3' 118s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.3' 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 118s ok 96 /driver/action_error/fail 118s # End of action_error tests 118s # Start of timeout tests 118s ok 97 /driver/timeout/cancelled 118s # End of timeout tests 118s # End of driver tests 118s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.3.test 118s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.3.test 118s TAP version 14 118s # random seed: R02S3e205de4f301aa995b9b8b170645e6f2 118s 1..14 118s # Start of device tests 118s # Start of async tests 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.3 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.3 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 1 /device/async/open 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 2 /device/async/close 118s # End of async tests 118s # Start of sync tests 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 3 /device/sync/open 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 4 /device/sync/close 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 5 /device/sync/get_driver 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 6 /device/sync/get_device_id 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 7 /device/sync/get_name 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 8 /device/sync/get_scan_type 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 9 /device/sync/get_nr_enroll_stages 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 10 /device/sync/supports_identify 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 11 /device/sync/supports_capture 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 12 /device/sync/has_storage 118s # Start of open tests 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 13 /device/sync/open/notify 118s # End of open tests 118s # Start of close tests 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765a987, GType is 107291160266624 118s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 118s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 118s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b0d7765453b, GType is 107291160271424 118s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # libfprint-device-DEBUG: Device reported close completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s ok 14 /device/sync/close/notify 118s # End of close tests 118s # End of sync tests 118s # End of device tests 118s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.3.test 118s Running test: libfprint-2/fp-context.test 118s TAP version 14 118s # random seed: R02S88ba19f1946684e6ae17eb5dae0cff92 118s 1..9 118s # Start of context tests 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 118s ok 1 /context/new 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 118s ok 2 /context/no-devices 118s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-SVBK22/virtual_image.socket 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 118s ok 3 /context/has-virtual-device 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 118s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FNCK22/virtual_image.socket 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 118s ok 4 /context/enumerates-new-devices 118s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-8SCK22/virtual_image.socket 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 118s ok 5 /context/remove-device-closed 118s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 118s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 118s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 118s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-H69J22/virtual_image.socket 118s # libfprint-context-DEBUG: created 118s # libfprint-device-DEBUG: Device reported probe completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:26.938: 86734499: ../libfprint/drivers/virtual-image.c:216 118s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_device_connection-DEBUG: 20:25:26.938: 86734556: ../libfprint/drivers/virtual-device-listener.c:153 118s # libfprint-image_device-DEBUG: Image device open completed 118s # libfprint-device-DEBUG: Device reported open completion 118s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 118s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 118s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:27.039: 86834835: ../libfprint/drivers/virtual-image.c:244 119s # libfprint-image_device-DEBUG: Image device close completed 119s # libfprint-device-DEBUG: Device reported close completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 119s ok 6 /context/remove-device-closing 119s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 119s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 119s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 119s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-RVO312/virtual_image.socket 119s # libfprint-context-DEBUG: created 119s # libfprint-device-DEBUG: Device reported probe completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:27.140: 86936132: ../libfprint/drivers/virtual-image.c:216 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_device_connection-DEBUG: 20:25:27.140: 86936155: ../libfprint/drivers/virtual-device-listener.c:153 119s # libfprint-image_device-DEBUG: Image device open completed 119s # libfprint-device-DEBUG: Device reported open completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:27.240: 87036494: ../libfprint/drivers/virtual-image.c:244 119s # libfprint-image_device-DEBUG: Image device close completed 119s # libfprint-device-DEBUG: Device reported close completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 119s ok 7 /context/remove-device-open 119s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 119s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 119s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 119s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-EEU712/virtual_image.socket 119s # libfprint-context-DEBUG: created 119s # libfprint-device-DEBUG: Device reported probe completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:27.342: 87138277: ../libfprint/drivers/virtual-image.c:216 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_device_connection-DEBUG: 20:25:27.342: 87138322: ../libfprint/drivers/virtual-device-listener.c:153 119s # libfprint-image_device-DEBUG: Image device open completed 119s # libfprint-device-DEBUG: Device reported open completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:27.443: 87238694: ../libfprint/drivers/virtual-image.c:244 119s # libfprint-image_device-DEBUG: Image device close completed 119s # libfprint-device-DEBUG: Device reported close completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 119s ok 8 /context/remove-device-opening 119s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 119s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 119s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 119s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-4WWB22/virtual_image.socket 119s # libfprint-context-DEBUG: created 119s # libfprint-device-DEBUG: Device reported probe completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:27.544: 87340338: ../libfprint/drivers/virtual-image.c:216 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_device_connection-DEBUG: 20:25:27.544: 87340361: ../libfprint/drivers/virtual-device-listener.c:153 119s # libfprint-image_device-DEBUG: Image device open completed 119s # libfprint-device-DEBUG: Device reported open completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # libfprint-image_device-DEBUG: Activating image device 119s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 119s # libfprint-image_device-DEBUG: Image device activation completed 119s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 119s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 119s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s # libfprint-image_device-DEBUG: Deactivating image device 119s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 119s # libfprint-image_device-DEBUG: Image device deactivation completed 119s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 119s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 119s # libfprint-device-DEBUG: Device reported enroll completion 119s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:3729): libfprint-virtual_image-DEBUG: 20:25:27.645: 87440960: ../libfprint/drivers/virtual-image.c:244 119s # libfprint-image_device-DEBUG: Image device close completed 119s # libfprint-device-DEBUG: Device reported close completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 119s ok 9 /context/remove-device-active 119s # End of context tests 119s PASS: libfprint-2/fp-context.test 119s Running test: libfprint-2/driver-egismoc.test 119s ** (umockdev-run:3753): DEBUG: 20:25:27.784: umockdev.vala:127: Created udev test bed /tmp/umockdev.1W4E22 119s ** (umockdev-run:3753): DEBUG: 20:25:27.785: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 119s ** (umockdev-run:3753): DEBUG: 20:25:27.786: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 119s ** (umockdev-run:3753): DEBUG: 20:25:27.790: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.1W4E22/dev/bus/usb/003/012 119s ** (umockdev-run:3753): DEBUG: 20:25:27.790: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 119s ** (umockdev-run:3753): DEBUG: 20:25:27.791: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 119s ** (umockdev-run:3753): DEBUG: 20:25:27.794: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.1W4E22/dev/bus/usb/003/001 119s ** (umockdev-run:3753): DEBUG: 20:25:27.795: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 119s ** (umockdev-run:3753): DEBUG: 20:25:27.795: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 119s (process:3757): libfprint-context-DEBUG: 20:25:27.874: Initializing FpContext (libfprint version 1.94.8+tod1) 119s (process:3757): libfprint-tod-DEBUG: 20:25:27.875: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.877: 87672618: ../libfprint/drivers/egismoc/egismoc.c:1597 119s (process:3757): libfprint-context-DEBUG: 20:25:27.877: No driver found for USB device 1D6B:0002 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.877: egismoc_probe enter --> 119s (process:3757): libfprint-device-DEBUG: 20:25:27.878: Device reported probe completion 119s (process:3757): libfprint-device-DEBUG: 20:25:27.878: Completing action FPI_DEVICE_ACTION_PROBE in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.878: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.879: Opening device 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.879: [egismoc] DEV_INIT_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.879: [egismoc] DEV_INIT_STATES entering state 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.880: [egismoc] DEV_INIT_STATES entering state 2 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.880: [egismoc] DEV_INIT_STATES entering state 3 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.881: [egismoc] DEV_INIT_STATES entering state 4 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.881: [egismoc] DEV_INIT_STATES entering state 5 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.881: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.881: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.881: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.882: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.882: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.882: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.882: Firmware version callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.882: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.882: Device firmware version is 9050.1.1.81 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.882: [egismoc] DEV_INIT_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.882: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.882: Device reported open completion 119s (process:3757): libfprint-device-DEBUG: 20:25:27.882: Completing action FPI_DEVICE_ACTION_OPEN in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.882: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.883: List 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.883: [egismoc] LIST_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.883: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.883: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.883: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.883: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.884: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Device fingerprint 3: FP1-20231016-3-5159A026-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Device fingerprint 4: FP1-20231016-4-A25C1212-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Number of currently enrolled fingerprints on the device is 7 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.884: [egismoc] LIST_STATES entering state 1 119s (process:3757): libfprint-device-DEBUG: 20:25:27.884: Device reported listing completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.884: [egismoc] LIST_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.884: Completing action FPI_DEVICE_ACTION_LIST in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.884: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Clear storage 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.884: [egismoc] DELETE_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.884: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.884: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.884: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.885: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Device fingerprint 3: FP1-20231016-3-5159A026-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Device fingerprint 4: FP1-20231016-4-A25C1212-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Number of currently enrolled fingerprints on the device is 7 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.885: [egismoc] DELETE_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Get delete command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.885: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.885: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.885: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.886: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.886: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.886: Delete callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.886: Response prefix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.886: Device reported deletion completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.886: [egismoc] DELETE_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.886: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.886: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.886: List 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.886: [egismoc] LIST_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.886: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.886: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.886: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.886: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.887: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.887: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.887: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.887: Number of currently enrolled fingerprints on the device is 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.887: [egismoc] LIST_STATES entering state 1 119s (process:3757): libfprint-device-DEBUG: 20:25:27.887: Device reported listing completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.887: [egismoc] LIST_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.887: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.887: Completing action FPI_DEVICE_ACTION_LIST in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (process:3757): libfprint-device-DEBUG: 20:25:27.887: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.887: Enroll 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.887: [egismoc] ENROLL_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.887: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.887: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.887: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.888: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.888: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.888: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.888: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.888: Number of currently enrolled fingerprints on the device is 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.888: [egismoc] ENROLL_STATES entering state 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.888: [egismoc] ENROLL_STATES entering state 2 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.888: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.888: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.888: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.889: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.889: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.889: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.889: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.889: [egismoc] ENROLL_STATES entering state 3 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.889: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.889: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.889: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.889: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.890: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.890: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.890: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.890: [egismoc] ENROLL_STATES entering state 4 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.890: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.890: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.890: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.890: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.890: [egismoc] ENROLL_STATES entering state 5 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.890: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.890: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.890: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.891: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.891: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.891: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.891: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.891: [egismoc] ENROLL_STATES entering state 6 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.891: Get check command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.891: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.891: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.891: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.891: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.892: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.892: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.892: Enroll check callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.892: Response suffix valid: yes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.892: [egismoc] ENROLL_STATES entering state 7 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.892: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.892: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.892: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.892: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.893: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.893: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.893: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.893: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.893: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.893: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.893: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.893: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.894: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.894: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.894: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.894: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.894: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.894: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.895: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.895: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.895: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.895: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.895: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.895: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.895: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.896: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Partial capture successful. Please touch the sensor again (1/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.896: Device reported enroll progress, reported 1 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.896: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.896: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.896: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.896: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.896: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.896: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.896: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.897: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.897: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.897: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.897: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.897: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.897: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.898: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.898: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.898: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.898: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.898: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Partial capture successful. Please touch the sensor again (2/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.898: Device reported enroll progress, reported 2 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.898: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.898: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.898: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.899: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.899: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.899: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.899: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.899: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.899: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.899: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.899: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.900: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.900: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.900: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.900: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.900: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.900: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.901: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.901: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.901: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.901: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.901: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.901: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.901: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.902: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.902: Device reported enroll progress, reported 2 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.902: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.902: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.902: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.902: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.903: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.903: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.903: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.903: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.903: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.903: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.903: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.903: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.903: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.903: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.903: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.903: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.903: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.904: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.904: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.904: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.904: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.904: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.904: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.904: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.905: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Partial capture successful. Please touch the sensor again (3/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.905: Device reported enroll progress, reported 3 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.905: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.905: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.905: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.905: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.906: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.906: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.906: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.906: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.906: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.906: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.906: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.906: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.906: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.906: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.906: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.906: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.907: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.907: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.907: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.907: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.907: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.907: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.907: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.908: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.908: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.908: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.908: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.908: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.908: Partial capture successful. Please touch the sensor again (4/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.908: Device reported enroll progress, reported 4 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.908: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.908: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.908: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.908: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.908: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.909: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.909: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.909: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.909: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.909: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.909: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.909: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.909: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.909: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.909: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.909: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.909: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.909: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.910: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.910: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.910: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.910: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.910: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.910: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.910: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.910: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.910: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.910: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.911: Device reported enroll progress, reported 4 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.911: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.911: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.911: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.911: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.911: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.911: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.911: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.912: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.912: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.912: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.912: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.912: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.912: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.913: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.913: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.913: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.913: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.913: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.913: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.913: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.914: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Partial capture successful. Please touch the sensor again (5/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.914: Device reported enroll progress, reported 5 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.914: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.914: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.914: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.914: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.914: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.914: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.914: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.915: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.915: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.915: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.915: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.915: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.915: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.916: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.916: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.916: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.916: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.916: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.916: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.916: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.916: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.916: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.916: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.916: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Partial capture successful. Please touch the sensor again (6/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.917: Device reported enroll progress, reported 6 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.917: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.917: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.917: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.917: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.917: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.917: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.917: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.918: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.918: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.918: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.918: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.918: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.918: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.919: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.919: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.919: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.919: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.919: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.919: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.919: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.920: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.920: Device reported enroll progress, reported 6 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.920: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.920: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.920: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.920: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.920: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.921: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.921: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.921: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.921: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.921: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.921: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.921: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.921: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.921: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.921: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.921: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.921: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.922: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.922: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.922: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.922: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.922: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.922: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.922: Device reported enroll progress, reported 6 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.923: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.923: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.923: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.923: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.923: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.923: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.923: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.923: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.923: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.923: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.923: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.923: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.924: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.924: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.924: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.924: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.924: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.924: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.924: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.925: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.925: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.925: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.925: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.925: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.925: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.925: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.926: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Partial capture successful. Please touch the sensor again (7/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.926: Device reported enroll progress, reported 7 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.926: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.926: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.926: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.926: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.926: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.926: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.926: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.927: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.927: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.927: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.927: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.927: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.927: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.927: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.927: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.927: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.927: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.927: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.928: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.928: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.928: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Partial capture successful. Please touch the sensor again (8/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.928: Device reported enroll progress, reported 8 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.928: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.928: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.928: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.929: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.929: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.929: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.929: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.929: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.929: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.929: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.929: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.929: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.930: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.930: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.930: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.930: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.930: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.930: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.930: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.930: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.930: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.930: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.930: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.931: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.931: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.931: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.931: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.931: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.931: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.931: Partial capture successful. Please touch the sensor again (9/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.931: Device reported enroll progress, reported 9 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.931: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.931: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.931: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.931: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.931: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.932: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.932: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.932: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.932: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.932: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.932: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.932: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.932: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.933: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.933: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.933: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.933: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.933: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.933: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.933: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.933: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.933: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.933: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.933: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.933: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.934: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.934: Device reported enroll progress, reported 9 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.934: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.934: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.934: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.934: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.935: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.935: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.935: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.935: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.935: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.935: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.935: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.935: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.936: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.936: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.936: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.936: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.936: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.936: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.936: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.936: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.936: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.936: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.936: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.936: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.936: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.937: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.937: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.937: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.937: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.937: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.937: Partial capture successful. Please touch the sensor again (10/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.937: Device reported enroll progress, reported 10 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.937: [egismoc] ENROLL_STATES entering state 12 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.937: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.937: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.937: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.937: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.938: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.938: [egismoc] ENROLL_STATES entering state 13 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: New fingerprint ID: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.938: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.938: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.938: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.938: [egismoc] ENROLL_STATES entering state 14 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.938: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.938: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.939: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.939: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.939: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.939: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.939: [egismoc] ENROLL_STATES entering state 15 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.939: Enrollment was successful! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.939: Device reported enroll completion 119s (process:3757): libfprint-device-DEBUG: 20:25:27.939: Device reported finger status change: FP_FINGER_STATUS_NONE 119s (process:3757): libfprint-device-DEBUG: 20:25:27.939: Print for finger FP_FINGER_LEFT_INDEX enrolled 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.939: [egismoc] ENROLL_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.939: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.939: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.939: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.939: List 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.939: [egismoc] LIST_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.939: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.939: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.939: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.940: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.940: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.940: [egismoc] LIST_STATES entering state 1 119s (process:3757): libfprint-device-DEBUG: 20:25:27.940: Device reported listing completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.940: [egismoc] LIST_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.940: Completing action FPI_DEVICE_ACTION_LIST in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.940: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-device-DEBUG: 20:25:27.940: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: Identify or Verify 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.940: [egismoc] IDENTIFY_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.940: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.940: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.941: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.941: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.941: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.941: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.941: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.941: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.941: [egismoc] IDENTIFY_STATES entering state 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.941: [egismoc] IDENTIFY_STATES entering state 2 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.941: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.941: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.941: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.942: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.942: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.942: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.942: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.942: [egismoc] IDENTIFY_STATES entering state 3 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.942: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.942: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.942: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.942: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.943: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.943: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.943: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.943: [egismoc] IDENTIFY_STATES entering state 4 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.943: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.943: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.943: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.943: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.943: [egismoc] IDENTIFY_STATES entering state 5 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.943: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.943: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.943: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.943: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.944: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.944: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.944: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.944: [egismoc] IDENTIFY_STATES entering state 6 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.944: Get check command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.944: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.944: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.944: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.944: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.945: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Identify check callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Identify successful for: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Verifying against: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-device-DEBUG: 20:25:27.945: Device reported verify result 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.945: [egismoc] IDENTIFY_STATES entering state 7 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.945: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.945: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.945: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.945: [egismoc] IDENTIFY_STATES entering state 8 119s (process:3757): libfprint-device-DEBUG: 20:25:27.945: Device reported verify completion 119s (process:3757): libfprint-device-DEBUG: 20:25:27.945: Device reported finger status change: FP_FINGER_STATUS_NONE 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.945: [egismoc] IDENTIFY_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.945: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.945: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.945: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-device-DEBUG: 20:25:27.946: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.946: Identify or Verify 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.946: [egismoc] IDENTIFY_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.946: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.946: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.946: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.946: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.947: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.947: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.947: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.947: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.947: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.947: [egismoc] IDENTIFY_STATES entering state 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.947: [egismoc] IDENTIFY_STATES entering state 2 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.947: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.947: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.947: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.947: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.948: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.948: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.948: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.948: [egismoc] IDENTIFY_STATES entering state 3 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.948: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.948: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.948: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.948: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.948: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.949: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.949: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.949: [egismoc] IDENTIFY_STATES entering state 4 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.949: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.949: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.949: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.949: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.949: [egismoc] IDENTIFY_STATES entering state 5 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.949: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.949: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.949: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.949: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.950: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.950: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.950: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.950: [egismoc] IDENTIFY_STATES entering state 6 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.950: Get check command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.950: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.950: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.950: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.950: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.951: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.951: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.951: Identify check callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.951: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.951: Identify successful for: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-device-DEBUG: 20:25:27.951: Device reported identify result 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.951: [egismoc] IDENTIFY_STATES entering state 7 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.951: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.951: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.951: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.951: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.952: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.952: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.952: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.952: [egismoc] IDENTIFY_STATES entering state 8 119s (process:3757): libfprint-device-DEBUG: 20:25:27.952: Device reported identify completion 119s (process:3757): libfprint-device-DEBUG: 20:25:27.952: Device reported finger status change: FP_FINGER_STATUS_NONE 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.952: [egismoc] IDENTIFY_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.952: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.952: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.952: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-device-DEBUG: 20:25:27.952: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.952: Enroll 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.952: [egismoc] ENROLL_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.952: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.952: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.952: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.952: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.953: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.953: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.953: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.953: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.953: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.953: [egismoc] ENROLL_STATES entering state 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.953: [egismoc] ENROLL_STATES entering state 2 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.953: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.953: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.953: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.953: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.954: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.954: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.954: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.954: [egismoc] ENROLL_STATES entering state 3 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.954: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.954: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.954: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.954: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.955: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.955: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.955: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.955: [egismoc] ENROLL_STATES entering state 4 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.955: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.955: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.955: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.955: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.955: [egismoc] ENROLL_STATES entering state 5 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.955: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.955: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.955: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.955: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.956: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.956: [egismoc] ENROLL_STATES entering state 6 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Get check command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.956: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.956: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.956: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Enroll check callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Response suffix valid: NO 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.956: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.956: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.956: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.956: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 119s (process:3757): libfprint-device-DEBUG: 20:25:27.956: Device reported enroll completion 119s (process:3757): libfprint-device-DEBUG: 20:25:27.956: Device reported finger status change: FP_FINGER_STATUS_NONE 119s (process:3757): libfprint-device-DEBUG: 20:25:27.956: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: List 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] LIST_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] LIST_STATES entering state 1 119s (process:3757): libfprint-device-DEBUG: 20:25:27.957: Device reported listing completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] LIST_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:27.957: Completing action FPI_DEVICE_ACTION_LIST in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:27.957: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-device-DEBUG: 20:25:27.957: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Enroll 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] ENROLL_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.957: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.957: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.958: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.958: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.958: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.958: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.958: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.958: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.958: [egismoc] ENROLL_STATES entering state 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.958: [egismoc] ENROLL_STATES entering state 2 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.958: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.958: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.958: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.959: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.959: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.959: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.959: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.959: [egismoc] ENROLL_STATES entering state 3 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.959: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.959: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.959: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.959: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.960: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.960: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.960: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.960: [egismoc] ENROLL_STATES entering state 4 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.960: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.960: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.960: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.960: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.960: [egismoc] ENROLL_STATES entering state 5 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.960: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.960: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.960: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.961: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.961: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.961: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.961: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.961: [egismoc] ENROLL_STATES entering state 6 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.961: Get check command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.961: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.961: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.961: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.961: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.962: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.962: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.962: Enroll check callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.962: Response suffix valid: yes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.962: [egismoc] ENROLL_STATES entering state 7 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.962: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.962: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.962: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.962: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.963: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.963: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.963: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.963: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.963: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.963: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.963: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.963: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.964: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.964: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.964: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.964: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.964: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.964: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.965: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.965: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.965: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.965: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.965: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.965: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.965: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.966: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.966: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.966: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.966: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.966: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.966: Partial capture successful. Please touch the sensor again (1/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.966: Device reported enroll progress, reported 1 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.966: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.966: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.966: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.966: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.966: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.967: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.967: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.967: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.967: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.967: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.967: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.967: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.967: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.967: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.967: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.967: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.967: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.967: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.968: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.968: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.968: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.968: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.968: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.968: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.968: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.969: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.969: Device reported enroll progress, reported 1 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.969: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.969: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.969: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.969: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.970: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.970: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.970: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.970: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.970: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.970: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.970: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.970: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.971: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.971: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.971: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.971: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.971: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.971: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.971: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.971: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.971: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.971: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.971: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.971: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.972: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.972: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.972: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.972: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.972: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.972: Partial capture successful. Please touch the sensor again (2/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.972: Device reported enroll progress, reported 2 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.972: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.972: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.972: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.972: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.972: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.973: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.973: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.973: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.973: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.973: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.973: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.973: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.973: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.974: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.974: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.974: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.974: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.974: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.974: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.974: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.974: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.974: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.974: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.974: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.974: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.975: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.975: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.975: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.975: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.975: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.975: Partial capture successful. Please touch the sensor again (3/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.975: Device reported enroll progress, reported 3 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.975: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.975: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.975: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.975: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.975: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.976: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.976: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.976: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.976: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.976: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.976: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.976: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.976: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.976: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.976: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.976: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.976: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.976: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.976: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.977: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.977: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.977: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.977: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.977: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.977: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.977: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.978: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.978: Device reported enroll progress, reported 3 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.978: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.978: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.978: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.978: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.979: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.979: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.979: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.979: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.979: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.979: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.979: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.979: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.979: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.979: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.979: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.979: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.979: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.980: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.980: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.980: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.980: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.980: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.980: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.980: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.981: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:27.981: Device reported enroll progress, reported 3 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.981: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.981: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.981: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.981: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.982: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.982: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.982: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.982: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.982: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.982: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.982: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.982: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.982: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.982: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.982: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.982: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.982: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.983: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.983: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.983: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.983: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.983: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.983: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.983: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.984: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.984: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.984: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.984: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.984: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.984: Partial capture successful. Please touch the sensor again (4/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.984: Device reported enroll progress, reported 4 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.984: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.984: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.984: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.984: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.984: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.985: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.985: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.985: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.985: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.985: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.985: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.985: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.985: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.985: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.985: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.985: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.985: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.985: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.986: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.986: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.986: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.986: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.986: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.986: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.986: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.987: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.987: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.987: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.987: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.987: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.987: Partial capture successful. Please touch the sensor again (5/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.987: Device reported enroll progress, reported 5 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.987: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.987: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.987: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.987: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.987: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.988: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.988: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.988: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.988: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.988: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.988: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.988: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.988: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.988: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.988: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.988: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.988: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.988: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.988: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.989: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.989: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.989: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.989: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.989: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.989: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.989: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.990: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.990: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.990: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.990: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.990: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.990: Partial capture successful. Please touch the sensor again (6/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.990: Device reported enroll progress, reported 6 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.990: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.990: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.990: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.990: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.990: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.991: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.991: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.991: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.991: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.991: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.991: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.991: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.991: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.992: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.992: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.992: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.992: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.992: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.992: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.992: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.992: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.992: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.992: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.992: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.992: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.993: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.993: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.993: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.993: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.993: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.993: Partial capture successful. Please touch the sensor again (7/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.993: Device reported enroll progress, reported 7 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.993: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.993: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.993: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.993: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.993: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.994: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.994: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.994: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.994: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.994: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.994: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.994: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.994: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.995: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.995: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.995: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.995: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.995: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.995: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.995: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.995: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.995: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.995: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.995: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.995: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.996: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.996: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.996: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.996: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.996: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.996: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.996: Partial capture successful. Please touch the sensor again (8/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.996: Device reported enroll progress, reported 8 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.996: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.996: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.996: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.996: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.996: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.997: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.997: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.997: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.997: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.997: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.997: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.997: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.997: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.998: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.998: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.998: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.998: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.998: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:27.998: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.998: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:27.998: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.998: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.998: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.998: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.998: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.999: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.999: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.999: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.999: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.999: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.999: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.999: Partial capture successful. Please touch the sensor again (9/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:27.999: Device reported enroll progress, reported 9 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.999: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.999: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:27.999: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.999: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:27.999: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.000: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.000: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.000: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.000: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.000: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.000: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.000: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.000: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.001: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.001: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.001: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.001: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.001: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:28.001: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.001: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:28.001: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.001: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.001: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.001: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.001: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.002: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.002: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:28.002: Device reported enroll progress, reported 9 of 10 have been completed 119s listing - device should have prints 119s clear device storage 119s clear done 119s listing - device should be empty 119s enrolling 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 1, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 2, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 3, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 4, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 5, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 6, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 7, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 8, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 9, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 10, , None, None) 119s enroll done 119s listing - device should have 1 print 119s verifying 119s verify done 119s async identifying 119s indentification_done: 119s try to enroll duplicate 119s duplicate enroll attempt done 119s listing - device should still only have 1 print 119s enroll new finger 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 1, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 2, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 3, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 4, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 5, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 6, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 7, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 8, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 9, , None, None) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:3757): libfprint-SSM-DEBUG: 20:25:28.002: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.002: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.002: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.002: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.003: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.003: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.003: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.003: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.003: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.003: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.003: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.003: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.003: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.003: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.003: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.004: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.004: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:28.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.004: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:28.004: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.004: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.004: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.004: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.004: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.004: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.005: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:28.005: Device reported enroll progress, reported 9 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.005: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.005: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.005: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.005: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.005: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.005: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.006: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.006: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.006: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.006: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.006: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.006: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.006: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.006: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.006: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:28.006: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:28.007: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.007: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.007: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.007: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.007: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Response suffix valid: NO 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Response suffix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:28.007: Device reported enroll progress, reported 9 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.007: [egismoc] ENROLL_STATES entering state 8 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.007: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.007: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.008: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.008: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.008: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.008: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.008: [egismoc] ENROLL_STATES entering state 9 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.008: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.008: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.008: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.009: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.009: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.009: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.009: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.009: [egismoc] ENROLL_STATES entering state 10 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.009: Wait for finger on sensor 119s (process:3757): libfprint-device-DEBUG: 20:25:28.009: Device reported finger status change: FP_FINGER_STATUS_NEEDED 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.009: Finger on sensor callback 119s (process:3757): libfprint-device-DEBUG: 20:25:28.009: Device reported finger status change: FP_FINGER_STATUS_PRESENT 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.009: [egismoc] ENROLL_STATES entering state 11 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.009: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.009: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.009: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.010: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.010: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.010: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.010: Read capture callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.010: Response prefix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.010: Response suffix valid: yes 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.010: Partial capture successful. Please touch the sensor again (10/10) 119s (process:3757): libfprint-device-DEBUG: 20:25:28.010: Device reported enroll progress, reported 10 of 10 have been completed 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.010: [egismoc] ENROLL_STATES entering state 12 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.010: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.010: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.010: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.010: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.011: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.011: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.011: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.011: [egismoc] ENROLL_STATES entering state 13 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.011: New fingerprint ID: FP1-00000000-7-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.011: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.011: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.011: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.011: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.012: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.012: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.012: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.012: [egismoc] ENROLL_STATES entering state 14 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.012: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.012: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.012: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.012: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.013: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.013: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.013: Task SSM next state callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.013: [egismoc] ENROLL_STATES entering state 15 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.013: Enrollment was successful! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.013: Device reported enroll completion 119s (process:3757): libfprint-device-DEBUG: 20:25:28.013: Device reported finger status change: FP_FINGER_STATUS_NONE 119s (process:3757): libfprint-device-DEBUG: 20:25:28.013: Print for finger FP_FINGER_RIGHT_INDEX enrolled 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.013: [egismoc] ENROLL_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.013: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:28.013: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.013: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.013: List 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.013: [egismoc] LIST_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.013: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.013: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.013: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.013: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.014: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Device fingerprint 2: FP1-00000000-7-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Number of currently enrolled fingerprints on the device is 2 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.014: [egismoc] LIST_STATES entering state 1 119s (process:3757): libfprint-device-DEBUG: 20:25:28.014: Device reported listing completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.014: [egismoc] LIST_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:28.014: Completing action FPI_DEVICE_ACTION_LIST in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.014: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Delete 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.014: [egismoc] DELETE_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.014: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.014: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.014: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.015: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Device fingerprint 1: FP1-00000000-2-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Device fingerprint 2: FP1-00000000-7-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Number of currently enrolled fingerprints on the device is 2 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.015: [egismoc] DELETE_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Get delete command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.015: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.015: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.015: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.016: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.016: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.016: Delete callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.016: Response prefix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:28.016: Device reported deletion completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.016: [egismoc] DELETE_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.016: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:28.016: Completing action FPI_DEVICE_ACTION_DELETE in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.016: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.016: List 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.016: [egismoc] LIST_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.016: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.016: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.016: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.016: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.017: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: Device fingerprint 1: FP1-00000000-7-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.017: [egismoc] LIST_STATES entering state 1 119s (process:3757): libfprint-device-DEBUG: 20:25:28.017: Device reported listing completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.017: [egismoc] LIST_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:28.017: Completing action FPI_DEVICE_ACTION_LIST in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: Clear storage 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.017: [egismoc] DELETE_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.017: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.017: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.017: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.018: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.018: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.018: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.018: Device fingerprint 1: FP1-00000000-7-00000000-nobody 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.018: Number of currently enrolled fingerprints on the device is 1 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.018: [egismoc] DELETE_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.018: Get delete command 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.018: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.018: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.018: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.019: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.019: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.019: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.019: Delete callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.019: Response prefix valid: yes 119s (process:3757): libfprint-device-DEBUG: 20:25:28.019: Device reported deletion completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.019: [egismoc] DELETE_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.019: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:28.019: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.019: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.019: List 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.019: [egismoc] LIST_STATES entering state 0 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.019: Execute command and get response 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.019: Get check bytes 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.019: [egismoc] CMD_STATES entering state 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.019: [egismoc] CMD_STATES entering state 1 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.020: Command receive callback 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.020: [egismoc] CMD_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.020: List callback 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.020: Number of currently enrolled fingerprints on the device is 0 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.020: [egismoc] LIST_STATES entering state 1 119s (process:3757): libfprint-device-DEBUG: 20:25:28.020: Device reported listing completion 119s (process:3757): libfprint-SSM-DEBUG: 20:25:28.020: [egismoc] LIST_STATES completed successfully 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.020: Task SSM done 119s (process:3757): libfprint-device-DEBUG: 20:25:28.020: Completing action FPI_DEVICE_ACTION_LIST in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.020: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.020: Closing device 119s (process:3757): libfprint-egismoc-DEBUG: 20:25:28.020: Cancel 119s (process:3757): libfprint-device-DEBUG: 20:25:28.020: Device reported close completion 119s (process:3757): libfprint-device-DEBUG: 20:25:28.021: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 119s (process:3757): libfprint-device-DEBUG: 20:25:28.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 119s 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 119s finger status: 119s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7f107bf1a3c0 (FpiDeviceEgisMoc at 0x176fa8c0)>, 10, , None, None) 119s enroll new finger done 119s listing - device should have 2 prints 119s deleting first print 119s delete done 119s listing - device should only have second print 119s clear device storage 119s clear done 119s listing - device should be empty 119s ** (umockdev-run:3753): DEBUG: 20:25:28.035: umockdev.vala:154: Removing test bed /tmp/umockdev.1W4E22 119s (umockdev-run:3753): GLib-DEBUG: 20:25:28.040: unsetenv() is not thread-safe and should not be used after threads are created 119s PASS: libfprint-2/driver-egismoc.test 119s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.94.7.test 119s TAP version 14 119s # random seed: R02S941e97e61c003b074f2cb2d9b080b862 119s 1..4 119s # Start of context tests 119s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 119s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 119s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7aa765e0a9d3, GType is 103984622919056 119s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 119s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 119s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7aa765e04b7b, GType is 103984622923728 119s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 119s ok 1 /context/new 119s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 119s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 119s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 119s ok 2 /context/no-devices 119s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 119s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 119s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7aa765e0a9d3, GType is 103984622919056 119s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 119s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 119s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7aa765e04b7b, GType is 103984622923728 119s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 119s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 119s # libfprint-context-DEBUG: created 119s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 119s # 119s # libfprint-device-DEBUG: Device reported probe completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 119s # 119s # libfprint-device-DEBUG: Device reported open completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 119s # 119s # libfprint-device-DEBUG: Device reported close completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s ok 3 /context/has-virtual-device 119s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 119s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 119s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7aa765e0a9d3, GType is 103984622919056 119s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 119s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 119s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7aa765e04b7b, GType is 103984622923728 119s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 119s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 119s # libfprint-context-DEBUG: created 119s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 119s # 119s # libfprint-device-DEBUG: Device reported probe completion 119s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 119s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 119s ok 4 /context/enumerates-new-devices 119s # End of context tests 120s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.94.7.test 120s Running test: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.1.test 120s TAP version 14 120s # random seed: R02S9e3464ff9ef9e48e6514700cb831cab2 120s 1..4 120s # Start of context tests 120s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 120s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 120s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x79b1624dd987, GType is 101149753478544 120s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 120s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.1 120s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 120s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x79b1624d753b, GType is 101149753483344 120s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 120s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.1 120s ok 1 /context/new 120s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 120s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 120s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 120s ok 2 /context/no-devices 120s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 120s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 120s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x79b1624dd987, GType is 101149753478544 120s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 120s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 120s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x79b1624d753b, GType is 101149753483344 120s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 120s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 120s # libfprint-context-DEBUG: created 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM_SINGLE_STATE entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM_SINGLE_STATE completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 14 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state -10 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 14 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state -10 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed successfully 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 120s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 121s # libfprint-device-DEBUG: Device reported probe completion 121s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 121s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 121s ok 3 /context/has-virtual-device # SKIP Not supported by TODv1 older than 1.92 121s # slow test /context/has-virtual-device executed in 1.03 secs 121s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 121s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 121s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x79b1624dd987, GType is 101149753478544 121s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 121s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 121s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x79b1624d753b, GType is 101149753483344 121s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 121s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 121s # libfprint-context-DEBUG: created 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM_SINGLE_STATE entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM_SINGLE_STATE completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 14 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state -10 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 2 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 3 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 14 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state -10 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM cancelled delayed state change 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed successfully 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 121s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed successfully 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.1] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 122s # libfprint-device-DEBUG: Device reported probe completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 4 /context/enumerates-new-devices # SKIP Not supported by TODv1 older than 1.92 122s # slow test /context/enumerates-new-devices executed in 1.03 secs 122s # End of context tests 122s PASS: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.1.test 122s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.1.test 122s (process:3787): libfprint-context-DEBUG: 20:25:30.140: Initializing FpContext (libfprint version 1.94.8+tod1) 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Found TOD entry point symbol 0x7f918309c987, GType is 101391421924160 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Initializing features for driver ssm_test_dev_tod_v1+1.90.1 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Found TOD entry point symbol 0x7f918309653b, GType is 101391421933968 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 122s (process:3787): libfprint-tod-DEBUG: 20:25:30.140: Initializing features for driver fake_test_dev_tod_v1+1.90.1 122s (process:3787): libfprint-context-DEBUG: 20:25:30.141: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 122s (process:3787): libfprint-context-DEBUG: 20:25:30.141: created 122s (process:3787): libfprint-device-DEBUG: 20:25:30.141: Device reported probe completion 122s (process:3787): libfprint-device-DEBUG: 20:25:30.141: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s (process:3787): libfprint-device-DEBUG: 20:25:30.141: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:3787): GLib-DEBUG: 20:25:30.141: setenv()/putenv() are not thread-safe and should not be used after threads are created 122s TAP version 14 122s # random seed: R02S4b16c4aadce3313df61473a29e564a1d 122s 1..97 122s # Start of driver tests 122s ok 1 /driver/get_driver 122s ok 2 /driver/get_device_id 122s ok 3 /driver/get_name 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 4 /driver/is_open 122s ok 5 /driver/get_nr_enroll_stages 122s ok 6 /driver/set_nr_enroll_stages 122s ok 7 /driver/supports_identify 122s ok 8 /driver/supports_capture 122s ok 9 /driver/has_storage 122s ok 10 /driver/do_not_support_identify 122s ok 11 /driver/do_not_support_capture 122s ok 12 /driver/has_not_storage 122s ok 13 /driver/get_usb_device 122s ok 14 /driver/get_virtual_env 122s ok 15 /driver/get_driver_data 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Device reported probe completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 16 /driver/initial_features 122s # libfprint-device-DEBUG: Device reported probe completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 17 /driver/probe 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 18 /driver/open 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 19 /driver/close 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 20 /driver/enroll 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 21 /driver/verify 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported identify result 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 22 /driver/identify 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported capture completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 23 /driver/capture 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported listing completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 24 /driver/list 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported deletion completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 25 /driver/delete 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 26 /driver/clear_storage # SKIP Feature not supported by TODv1 versions before 1.92.0 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 122s # libfprint-device-DEBUG: Device reported deletion completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 27 /driver/cancel 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 28 /driver/critical # SKIP Feature not supported by TODv1 versions before 1.94.0 122s ok 29 /driver/get_current_action 122s ok 30 /driver/timeout 122s ok 31 /driver/error_types 122s ok 32 /driver/retry_error_types 122s # Start of get_scan_type tests 122s ok 33 /driver/get_scan_type/press 122s ok 34 /driver/get_scan_type/swipe 122s # End of get_scan_type tests 122s # Start of set_scan_type tests 122s ok 35 /driver/set_scan_type/press 122s ok 36 /driver/set_scan_type/swipe 122s # End of set_scan_type tests 122s # Start of finger_status tests 122s ok 37 /driver/finger_status/inactive 122s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 122s ok 38 /driver/finger_status/waiting 122s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 122s ok 39 /driver/finger_status/present 122s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 122s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 122s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 122s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 122s ok 40 /driver/finger_status/changes 122s # End of finger_status tests 122s # Start of features tests 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 41 /driver/features/probe_updates # SKIP Feature not supported by TODv1 versions before 1.92.0 122s # End of features tests 122s # Start of initial_features tests 122s ok 42 /driver/initial_features/none 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 43 /driver/initial_features/no_capture 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 44 /driver/initial_features/no_verify 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 45 /driver/initial_features/no_identify 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 46 /driver/initial_features/no_storage 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 47 /driver/initial_features/no_list 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 48 /driver/initial_features/no_delete 122s ok 49 /driver/initial_features/no_clear 122s # End of initial_features tests 122s # Start of probe tests 122s # libfprint-device-DEBUG: Device reported probe completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 50 /driver/probe/error 122s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 122s # libfprint-device-DEBUG: Device reported probe completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 51 /driver/probe/action_error 122s # End of probe tests 122s # Start of open tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 52 /driver/open/error 122s # End of open tests 122s # Start of close tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 53 /driver/close/error 122s # End of close tests 122s # Start of enroll tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 54 /driver/enroll/error 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported enroll progress, reported 2139055100 of 1696068004 have been completed 122s # libfprint-device-DEBUG: Device reported enroll progress, reported 1854649455 of 1696068004 have been completed 122s # libfprint-device-DEBUG: Device reported enroll progress, reported 1792444573 of 1696068004 have been completed 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 55 /driver/enroll/progress 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 56 /driver/enroll/update_nbis 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 57 /driver/enroll/update_nbis_wrong_device 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 58 /driver/enroll/update_nbis_wrong_driver 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 59 /driver/enroll/update_nbis_missing_feature 122s # Start of error tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 60 /driver/enroll/error/no_print 122s # End of error tests 122s # End of enroll tests 122s # Start of verify tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 61 /driver/verify/fail 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 62 /driver/verify/retry 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 63 /driver/verify/error 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 64 /driver/verify/not_supported 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 65 /driver/verify/report_no_cb 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 66 /driver/verify/not_reported 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported verify result 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 67 /driver/verify/complete_retry 122s # End of verify tests 122s # Start of identify tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported identify result 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 68 /driver/identify/fail 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported identify result 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 122s ok 69 /driver/identify/retry 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 122s ok 70 /driver/identify/error 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 122s ok 71 /driver/identify/not_reported 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported identify result 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported identify result 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported identify result 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 72 /driver/identify/complete_retry 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported identify result 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 73 /driver/identify/report_no_cb 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 74 /driver/identify/suspend_continues # SKIP Feature not supported by TODv1 versions before 1.94.0 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 75 /driver/identify/suspend_succeeds # SKIP Feature not supported by TODv1 versions before 1.94.0 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 76 /driver/identify/suspend_busy_error # SKIP Feature not supported by TODv1 versions before 1.94.0 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 77 /driver/identify/suspend_while_idle # SKIP Feature not supported by TODv1 versions before 1.94.0 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 78 /driver/identify/warmup_cooldown # SKIP Feature not supported by TODv1 versions before 1.94.0 122s # End of identify tests 122s # Start of capture tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 79 /driver/capture/not_supported 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported capture completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 80 /driver/capture/error 122s # End of capture tests 122s # Start of list tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported listing completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 81 /driver/list/error 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 82 /driver/list/no_storage 122s # End of list tests 122s # Start of delete tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported deletion completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 83 /driver/delete/error 122s # End of delete tests 122s # Start of clear_storage tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 84 /driver/clear_storage/error # SKIP Feature not supported by TODv1 versions before 1.92.0 122s # End of clear_storage tests 122s # Start of cancel tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported deletion completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 85 /driver/cancel/fail 122s # End of cancel tests 122s # Start of get_current_action tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 86 /driver/get_current_action/open 122s # End of get_current_action tests 122s # Start of get_cancellable tests 122s ok 87 /driver/get_cancellable/error 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 88 /driver/get_cancellable/open 122s # Start of open tests 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 89 /driver/get_cancellable/open/internal 122s # End of open tests 122s # End of get_cancellable tests 122s # Start of action_is_cancelled tests 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 90 /driver/action_is_cancelled/open # SKIP Feature not supported by TODv1 versions before 1.94.0 122s ok 91 /driver/action_is_cancelled/error 122s # Start of open tests 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s ok 92 /driver/action_is_cancelled/open/internal # SKIP Feature not supported by TODv1 versions before 1.94.0 122s # End of open tests 122s # End of action_is_cancelled tests 122s # Start of complete_action tests 122s # Start of all tests 122s ok 93 /driver/complete_action/all/error 122s # End of all tests 122s # End of complete_action tests 122s # Start of action_error tests 122s ok 94 /driver/action_error/error 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 122s # libfprint-device-DEBUG: Device reported capture completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 122s # libfprint-device-DEBUG: Device reported listing completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 122s # libfprint-device-DEBUG: Device reported deletion completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 95 /driver/action_error/all 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported enroll completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported verify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported identify completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported capture completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported listing completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Device reported deletion completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.1' 122s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.1' 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 122s ok 96 /driver/action_error/fail 122s # End of action_error tests 122s # Start of timeout tests 122s ok 97 /driver/timeout/cancelled 122s # End of timeout tests 122s # End of driver tests 122s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.1.test 122s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.2.test 122s TAP version 14 122s # random seed: R02Sdce219f7492290691c283bebf19e83ae 122s 1..4 122s # Start of context tests 122s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7d3f0a251987, GType is 110367493750160 122s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 122s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.2 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7d3f0d4de53b, GType is 110367493754960 122s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 122s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.2 122s ok 1 /context/new 122s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 122s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 122s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 122s ok 2 /context/no-devices 122s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7d3f0a251987, GType is 110367493750160 122s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7d3f0d4de53b, GType is 110367493754960 122s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 122s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 122s # libfprint-context-DEBUG: created 122s # libfprint-device-DEBUG: Device reported probe completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported open completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s # libfprint-device-DEBUG: Device reported close completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 3 /context/has-virtual-device 122s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7d3f0a251987, GType is 110367493750160 122s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7d3f0d4de53b, GType is 110367493754960 122s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 122s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 122s # libfprint-context-DEBUG: created 122s # libfprint-device-DEBUG: Device reported probe completion 122s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 122s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 122s ok 4 /context/enumerates-new-devices 122s # End of context tests 122s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.2.test 122s Running test: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.3.test 122s TAP version 14 122s # random seed: R02S276462a4e22ba1b684ff5ed04a98f568 122s 1..4 122s # Start of context tests 122s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7fceaa096987, GType is 104525947010448 122s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 122s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.3 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7fceaa09053b, GType is 104525947015248 122s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 122s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.3 122s ok 1 /context/new 122s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 122s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 122s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 122s ok 2 /context/no-devices 122s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7fceaa096987, GType is 104525947010448 122s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 122s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 122s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7fceaa09053b, GType is 104525947015248 122s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 122s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 122s # libfprint-context-DEBUG: created 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM_SINGLE_STATE entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM_SINGLE_STATE completed successfully 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 14 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state -10 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 122s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 14 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state -10 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 123s # libfprint-device-DEBUG: Device reported probe completion 123s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 123s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 123s ok 3 /context/has-virtual-device # SKIP Not supported by TODv1 older than 1.92 123s # slow test /context/has-virtual-device executed in 1.03 secs 123s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 123s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 123s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7fceaa096987, GType is 104525947010448 123s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 123s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 123s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7fceaa09053b, GType is 104525947015248 123s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 123s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 123s # libfprint-context-DEBUG: created 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM_SINGLE_STATE entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM_SINGLE_STATE completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 14 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state -10 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 123s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 2 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 3 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 14 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state -10 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 124s Executing: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.3.test 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed successfully 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM cancelled delayed state change 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 1 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed successfully 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed successfully 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed successfully 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 1 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM entering state 0 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 124s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.3] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 124s # libfprint-device-DEBUG: Device reported probe completion 124s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 124s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 124s ok 4 /context/enumerates-new-devices # SKIP Not supported by TODv1 older than 1.92 124s # slow test /context/enumerates-new-devices executed in 1.03 secs 124s # End of context tests 124s PASS: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.3.test 124s Running test: libfprint-2/driver-focaltech_moc.test 124s ** (umockdev-run:3821): DEBUG: 20:25:32.449: umockdev.vala:127: Created udev test bed /tmp/umockdev.T3A812 124s ** (umockdev-run:3821): DEBUG: 20:25:32.450: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 124s ** (umockdev-run:3821): DEBUG: 20:25:32.453: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 124s ** (umockdev-run:3821): DEBUG: 20:25:32.456: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.T3A812/dev/bus/usb/003/006 124s ** (umockdev-run:3821): DEBUG: 20:25:32.456: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 124s ** (umockdev-run:3821): DEBUG: 20:25:32.459: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 124s ** (umockdev-run:3821): DEBUG: 20:25:32.462: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.T3A812/dev/bus/usb/003/002 124s ** (umockdev-run:3821): DEBUG: 20:25:32.462: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 124s ** (umockdev-run:3821): DEBUG: 20:25:32.465: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 124s ** (umockdev-run:3821): DEBUG: 20:25:32.467: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.T3A812/dev/bus/usb/003/001 124s ** (umockdev-run:3821): DEBUG: 20:25:32.467: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 124s ** (umockdev-run:3821): DEBUG: 20:25:32.469: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 124s ** (umockdev-run:3821): DEBUG: 20:25:32.472: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4 124s ** (umockdev-run:3821): DEBUG: 20:25:32.472: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 124s (process:3825): libfprint-context-DEBUG: 20:25:32.544: Initializing FpContext (libfprint version 1.94.8+tod1) 124s (process:3825): libfprint-tod-DEBUG: 20:25:32.544: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.546: 92342317: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1849 124s (process:3825): libfprint-context-DEBUG: 20:25:32.546: No driver found for USB device 05E3:0608 124s (process:3825): libfprint-context-DEBUG: 20:25:32.546: No driver found for USB device 1D6B:0002 124s (process:3825): libfprint-device-DEBUG: 20:25:32.547: Device reported probe completion 124s (process:3825): libfprint-device-DEBUG: 20:25:32.547: Completing action FPI_DEVICE_ACTION_PROBE in idle! 124s (process:3825): libfprint-device-DEBUG: 20:25:32.547: Not updating temperature model, device can run continuously! 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.548: class:dc, subclass:a0, protocol:b0 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.548: bytes size:0 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.548: kind:5, max packet size:64, poll interval:0, refresh:0, sync address:0, address:2, number:2, direction:G_USB_DEVICE_DIRECTION_HOST_TO_DEVICE 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.548: bytes size:0 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.548: kind:5, max packet size:64, poll interval:0, refresh:0, sync address:0, address:81, number:1, direction:G_USB_DEVICE_DIRECTION_DEVICE_TO_HOST 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.548: [focaltech_moc] DEV_INIT_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.548: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.549: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.549: focaltechmoc enroll_times: 10 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.549: [focaltech_moc] DEV_INIT_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.549: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.550: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.550: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.550: [focaltech_moc] DEV_INIT_STATES completed successfully 124s (process:3825): libfprint-device-DEBUG: 20:25:32.550: Device reported open completion 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.550: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-device-DEBUG: 20:25:32.550: Completing action FPI_DEVICE_ACTION_OPEN in idle! 124s (process:3825): libfprint-device-DEBUG: 20:25:32.550: Not updating temperature model, device can run continuously! 124s (process:3825): libfprint-device-DEBUG: 20:25:32.551: Not updating temperature model, device can run continuously! 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.551: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.551: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.551: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.552: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.552: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.552: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.552: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.553: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.553: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.553: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.553: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.553: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.553: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.554: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.554: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.554: focaltechmoc user id: FP1-00000000-0-00000000-nobody 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.554: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.554: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.554: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.555: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.555: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.555: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 124s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.605: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.605: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.605: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.606: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.606: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.656: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.656: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.656: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.657: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.657: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.707: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.707: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.707: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.708: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.708: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.758: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.758: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.758: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.758: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.758: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.808: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.809: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.809: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.809: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.809: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.859: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.859: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.860: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.860: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.860: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.860: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.861: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-device-DEBUG: 20:25:32.861: Device reported enroll progress, reported 1 of 10 have been completed 124s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:32.861: focaltechmoc remain: 9 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.861: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.861: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.861: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.861: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.862: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.862: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.912: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.912: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.912: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.913: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.913: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.963: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.963: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.963: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.964: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 124s (process:3825): libfprint-SSM-DEBUG: 20:25:32.964: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.014: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.014: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.014: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.014: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.015: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.065: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.065: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.065: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.066: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.066: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.116: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.116: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.116: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.116: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.117: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.117: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.117: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-device-DEBUG: 20:25:33.117: Device reported enroll progress, reported 2 of 10 have been completed 125s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:33.117: focaltechmoc remain: 8 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.117: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.117: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.118: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.118: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.118: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.118: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.168: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.168: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.169: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.169: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.169: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.170: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.170: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-device-DEBUG: 20:25:33.170: Device reported enroll progress, reported 3 of 10 have been completed 125s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:33.170: focaltechmoc remain: 7 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.170: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.170: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.170: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.171: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.171: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.171: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.221: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.221: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.222: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.222: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.222: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.272: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.272: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.273: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.273: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.273: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.323: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.324: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.324: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.324: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.374: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.374: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.374: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.375: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.375: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.425: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.425: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.425: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.426: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.426: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.426: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.426: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-device-DEBUG: 20:25:33.427: Device reported enroll progress, reported 4 of 10 have been completed 125s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:33.427: focaltechmoc remain: 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.427: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.427: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.427: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.427: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.428: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.428: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.478: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.478: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.479: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.479: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.529: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.529: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.529: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.530: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.530: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.580: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.580: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.580: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.581: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.581: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.581: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.581: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-device-DEBUG: 20:25:33.582: Device reported enroll progress, reported 5 of 10 have been completed 125s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:33.582: focaltechmoc remain: 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.582: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.582: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.582: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.582: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.583: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.583: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.633: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.633: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.633: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.634: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.634: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.684: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.684: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.684: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.685: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.685: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.735: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.735: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.735: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.736: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.736: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.786: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.786: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.786: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.786: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.786: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.787: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.787: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-device-DEBUG: 20:25:33.787: Device reported enroll progress, reported 6 of 10 have been completed 125s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:33.787: focaltechmoc remain: 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.787: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.787: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.788: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.788: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.788: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.788: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.788: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.789: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-device-DEBUG: 20:25:33.789: Device reported enroll progress, reported 6 of 10 have been completed 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.789: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.789: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.789: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.789: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.790: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.790: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.840: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.840: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.840: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.841: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.841: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.891: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.891: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.891: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.892: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.892: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.942: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.942: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.943: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.943: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.943: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.993: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.993: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.993: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.994: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.994: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.994: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.994: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-device-DEBUG: 20:25:33.995: Device reported enroll progress, reported 7 of 10 have been completed 125s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:33.995: focaltechmoc remain: 3 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.995: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.995: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.995: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.995: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.996: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 125s (process:3825): libfprint-SSM-DEBUG: 20:25:33.996: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.046: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.046: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.046: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.047: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.047: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.097: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.097: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.097: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.098: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.098: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.098: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.098: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-device-DEBUG: 20:25:34.099: Device reported enroll progress, reported 8 of 10 have been completed 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.099: focaltechmoc remain: 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.099: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.099: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.099: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.099: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.100: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.100: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.150: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.150: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.150: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.150: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.150: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.151: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.151: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-device-DEBUG: 20:25:34.151: Device reported enroll progress, reported 9 of 10 have been completed 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.151: focaltechmoc remain: 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.151: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.151: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.152: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.152: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.152: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.152: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.202: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.202: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.203: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.203: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.203: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.204: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.204: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-device-DEBUG: 20:25:34.204: Device reported enroll progress, reported 10 of 10 have been completed 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.204: focaltechmoc remain: 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.204: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.204: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.204: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.205: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.205: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.205: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.205: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.205: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.206: focaltech_moc_commit_cb success 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.206: Enrollment was successful! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.206: Device reported enroll completion 126s (process:3825): libfprint-device-DEBUG: 20:25:34.206: Print for finger FP_FINGER_UNKNOWN enrolled 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.206: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.206: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-device-DEBUG: 20:25:34.206: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.206: Not updating temperature model, device can run continuously! 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.206: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.206: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.206: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.207: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.207: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.207: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.207: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.208: focaltechmoc add slot: 0 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.208: FP1-00000000-0-00000000-nobody 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.208: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 126s (process:3825): libfprint-device-DEBUG: 20:25:34.208: Device reported listing completion 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.208: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.208: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-device-DEBUG: 20:25:34.208: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.208: Not updating temperature model, device can run continuously! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.208: Not updating temperature model, device can run continuously! 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.208: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.208: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.208: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.209: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.209: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.209: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.209: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.210: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.210: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.260: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.260: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.260: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.261: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.261: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.311: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.311: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.311: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.312: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.312: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.362: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.362: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.362: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.363: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.363: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.413: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.413: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.413: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.414: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.414: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.414: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.414: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.415: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.415: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.415: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.415: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-device-DEBUG: 20:25:34.416: Device reported verify result 126s (process:3825): libfprint-device-DEBUG: 20:25:34.416: Device reported verify completion 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.416: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.416: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-device-DEBUG: 20:25:34.416: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.416: Not updating temperature model, device can run continuously! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.416: Not updating temperature model, device can run continuously! 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.416: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.416: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.417: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.417: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.417: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.417: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.417: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.418: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.418: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.468: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.468: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.468: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.469: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.469: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.519: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.519: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.519: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.520: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.520: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.521: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.521: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.521: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.521: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.521: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.522: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-device-DEBUG: 20:25:34.522: Device reported identify result 126s (process:3825): libfprint-device-DEBUG: 20:25:34.522: Device reported identify completion 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.522: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.522: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-device-DEBUG: 20:25:34.522: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.522: Not updating temperature model, device can run continuously! 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.523: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.523: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.523: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.524: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.524: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.524: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.524: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.524: focaltechmoc add slot: 0 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.524: FP1-00000000-0-00000000-nobody 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.524: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.524: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.525: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.525: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.525: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.525: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.526: delete slot 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 126s (process:3825): libfprint-device-DEBUG: 20:25:34.526: Device reported deletion completion 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 126s (process:3825): libfprint-device-DEBUG: 20:25:34.526: Completing action FPI_DEVICE_ACTION_DELETE in idle! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.526: Not updating temperature model, device can run continuously! 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.526: Focaltechmoc dev_exit 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] DEV_EXIT_STATES entering state 0 126s (process:3825): libfprint-SSM-DEBUG: 20:25:34.526: [focaltech_moc] DEV_EXIT_STATES completed successfully 126s (process:3825): libfprint-focaltech_moc-DEBUG: 20:25:34.526: class:dc, subclass:a0, protocol:b0 126s (process:3825): libfprint-device-DEBUG: 20:25:34.527: Device reported close completion 126s (process:3825): libfprint-device-DEBUG: 20:25:34.527: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 126s (process:3825): libfprint-device-DEBUG: 20:25:34.527: Not updating temperature model, device can run continuously! 126s enrolling 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 1, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 2, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 3, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 4, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 5, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 6, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 7, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 8, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 9, None, None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x74808fbf5b80 (FpiDeviceFocaltechMoc at 0x324d82f0)>, 10, None, None, None) 126s enroll done 126s listing 126s listing done 126s verifying 126s verify done 126s async identifying 126s indentification_done: 126s deleting 126s delete done 126s ** (umockdev-run:3821): DEBUG: 20:25:34.540: umockdev.vala:154: Removing test bed /tmp/umockdev.T3A812 126s (umockdev-run:3821): GLib-DEBUG: 20:25:34.549: unsetenv() is not thread-safe and should not be used after threads are created 126s PASS: libfprint-2/driver-focaltech_moc.test 126s Running test: libfprint-2/driver-egismoc-05a1.test 126s ** (umockdev-run:3833): DEBUG: 20:25:34.589: umockdev.vala:127: Created udev test bed /tmp/umockdev.A1XA22 126s ** (umockdev-run:3833): DEBUG: 20:25:34.589: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 126s ** (umockdev-run:3833): DEBUG: 20:25:34.590: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 126s ** (umockdev-run:3833): DEBUG: 20:25:34.594: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.A1XA22/dev/bus/usb/001/003 126s ** (umockdev-run:3833): DEBUG: 20:25:34.594: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 126s ** (umockdev-run:3833): DEBUG: 20:25:34.595: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 126s ** (umockdev-run:3833): DEBUG: 20:25:34.598: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.A1XA22/dev/bus/usb/001/001 126s ** (umockdev-run:3833): DEBUG: 20:25:34.598: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 126s ** (umockdev-run:3833): DEBUG: 20:25:34.599: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 126s (process:3837): libfprint-context-DEBUG: 20:25:34.672: Initializing FpContext (libfprint version 1.94.8+tod1) 126s (process:3837): libfprint-tod-DEBUG: 20:25:34.672: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.674: 94469813: ../libfprint/drivers/egismoc/egismoc.c:1597 126s (process:3837): libfprint-context-DEBUG: 20:25:34.674: No driver found for USB device 1D6B:0002 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.674: egismoc_probe enter --> 126s (process:3837): libfprint-device-DEBUG: 20:25:34.675: Device reported probe completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.675: Completing action FPI_DEVICE_ACTION_PROBE in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.676: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.676: Opening device 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.677: [egismoc] DEV_INIT_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.677: [egismoc] DEV_INIT_STATES entering state 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.677: [egismoc] DEV_INIT_STATES entering state 2 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.678: [egismoc] DEV_INIT_STATES entering state 3 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.678: [egismoc] DEV_INIT_STATES entering state 4 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.679: [egismoc] DEV_INIT_STATES entering state 5 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.679: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.679: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.679: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.679: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.680: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.680: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.680: Firmware version callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.680: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.680: Device firmware version is 9050.1.2.13 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.680: [egismoc] DEV_INIT_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.680: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.680: Device reported open completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.680: Completing action FPI_DEVICE_ACTION_OPEN in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.680: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.680: List 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.680: [egismoc] LIST_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.681: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.681: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.681: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Number of currently enrolled fingerprints on the device is 3 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.681: [egismoc] LIST_STATES entering state 1 126s (process:3837): libfprint-device-DEBUG: 20:25:34.681: Device reported listing completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.681: [egismoc] LIST_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.681: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.681: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.681: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.682: Clear storage 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.682: [egismoc] DELETE_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.682: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.682: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.682: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.682: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.682: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.683: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Number of currently enrolled fingerprints on the device is 3 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.683: [egismoc] DELETE_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Get delete command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.683: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.683: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.683: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.683: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Delete callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Response prefix valid: yes 126s (process:3837): libfprint-device-DEBUG: 20:25:34.684: Device reported deletion completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.684: [egismoc] DELETE_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.684: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.684: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: List 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.684: [egismoc] LIST_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.684: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.684: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.684: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Number of currently enrolled fingerprints on the device is 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.684: [egismoc] LIST_STATES entering state 1 126s (process:3837): libfprint-device-DEBUG: 20:25:34.684: Device reported listing completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.684: [egismoc] LIST_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.684: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.684: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.684: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 126s (process:3837): libfprint-device-DEBUG: 20:25:34.685: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.685: Enroll 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.685: [egismoc] ENROLL_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.685: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.685: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.685: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.685: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.686: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.686: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.686: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.686: Number of currently enrolled fingerprints on the device is 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.686: [egismoc] ENROLL_STATES entering state 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.686: [egismoc] ENROLL_STATES entering state 2 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.686: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.686: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.686: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.686: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.687: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.687: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.687: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.687: [egismoc] ENROLL_STATES entering state 3 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.687: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.687: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.687: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.687: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.688: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.688: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.688: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.688: [egismoc] ENROLL_STATES entering state 4 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.688: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.688: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.688: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.688: [egismoc] ENROLL_STATES entering state 5 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.688: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.688: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.688: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.689: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.689: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.689: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.689: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.689: [egismoc] ENROLL_STATES entering state 6 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.689: Get check command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.689: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.689: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.689: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.689: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.690: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.690: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.690: Enroll check callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.690: Response suffix valid: yes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.690: [egismoc] ENROLL_STATES entering state 7 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.690: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.690: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.690: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.690: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.691: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.691: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.691: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.691: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.691: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.691: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.691: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.691: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.692: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.692: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.692: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.692: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.692: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.692: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.692: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.693: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.693: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.693: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.693: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.693: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.693: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.693: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.694: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.694: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.694: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.694: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.694: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.694: Partial capture successful. Please touch the sensor again (1/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.694: Device reported enroll progress, reported 1 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.694: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.694: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.694: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.694: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.694: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.695: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.695: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.695: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.695: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.695: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.695: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.695: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.695: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.696: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.696: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.696: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.696: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.696: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.696: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.696: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.696: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.696: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.696: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.696: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.696: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.696: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.697: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.697: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.697: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.697: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.697: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.697: Partial capture successful. Please touch the sensor again (2/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.697: Device reported enroll progress, reported 2 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.697: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.697: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.697: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.697: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.697: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.698: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.698: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.698: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.698: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.698: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.698: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.698: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.698: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.698: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.698: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.698: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.698: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.698: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.698: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.699: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.699: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.699: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.699: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.699: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.699: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.699: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.700: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Response prefix valid: NO 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Response prefix valid: NO 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Response prefix valid: yes 126s (process:3837): libfprint-device-DEBUG: 20:25:34.700: Device reported enroll progress, reported 2 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.700: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.700: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.700: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.700: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.700: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.700: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.701: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.701: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.701: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.702: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.702: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.702: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.702: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.702: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.702: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.702: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.702: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.702: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.702: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.702: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.703: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.703: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.703: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.703: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.703: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.703: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.703: Partial capture successful. Please touch the sensor again (3/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.703: Device reported enroll progress, reported 3 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.704: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.704: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.704: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.704: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.704: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.705: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.705: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.705: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.705: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.705: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.705: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.705: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.705: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.706: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.706: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.706: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.706: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.706: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.706: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.706: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.706: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.706: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.706: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.706: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.707: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.707: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.707: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.707: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.707: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.707: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.707: Partial capture successful. Please touch the sensor again (4/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.707: Device reported enroll progress, reported 4 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.707: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.707: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.707: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.707: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.708: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.708: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.708: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.708: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.709: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.709: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.709: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.709: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.709: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.709: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.710: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.710: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.710: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.710: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.710: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.710: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.710: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.710: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.710: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.710: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.710: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.710: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.711: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.711: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.711: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.711: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.711: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.711: Partial capture successful. Please touch the sensor again (5/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.711: Device reported enroll progress, reported 5 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.711: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.711: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.711: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.711: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.711: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.712: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.712: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.712: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.712: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.712: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.712: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.712: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.713: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.713: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.713: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.713: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.713: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.713: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.714: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.714: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.714: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.714: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.714: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.714: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.714: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.715: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.715: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.715: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.715: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.715: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.715: Partial capture successful. Please touch the sensor again (6/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.715: Device reported enroll progress, reported 6 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.715: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.715: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.715: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.715: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.715: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.716: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.716: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.716: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.716: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.716: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.716: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.716: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.716: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.717: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.717: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.717: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.717: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.717: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.717: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.717: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.717: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.717: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.717: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.717: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.717: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.718: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.718: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.718: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.718: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.718: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.718: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.718: Partial capture successful. Please touch the sensor again (7/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.718: Device reported enroll progress, reported 7 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.718: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.718: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.718: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.718: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.719: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.719: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.719: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.719: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.720: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.720: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.720: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.720: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.720: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.721: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.721: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.721: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.721: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.721: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.721: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.721: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.721: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.721: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.721: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.721: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.721: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.722: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.722: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.722: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.722: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.722: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.722: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.722: Partial capture successful. Please touch the sensor again (8/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.722: Device reported enroll progress, reported 8 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.722: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.722: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.722: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.722: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.723: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.723: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.723: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.723: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.723: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.723: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.723: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.723: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.724: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.724: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.724: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.724: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.724: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.724: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.725: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.725: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.725: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.725: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.725: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.725: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.725: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.726: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.726: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.726: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.726: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.726: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.726: Partial capture successful. Please touch the sensor again (9/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.726: Device reported enroll progress, reported 9 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.726: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.726: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.726: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.726: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.726: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.727: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.727: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.727: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.727: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.727: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.727: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.727: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.728: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.728: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.728: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.728: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.728: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.728: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.729: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.729: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.729: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.729: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.729: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.729: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.729: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.730: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.730: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.730: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.730: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.730: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.730: Partial capture successful. Please touch the sensor again (10/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.730: Device reported enroll progress, reported 10 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.730: [egismoc] ENROLL_STATES entering state 12 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.730: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.730: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.730: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.730: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.731: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.731: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.731: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.731: [egismoc] ENROLL_STATES entering state 13 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.731: New fingerprint ID: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.731: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.731: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.731: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.732: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.732: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.732: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.732: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.732: [egismoc] ENROLL_STATES entering state 14 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.732: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.732: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.732: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.733: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.733: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.733: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.733: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.733: [egismoc] ENROLL_STATES entering state 15 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.733: Enrollment was successful! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.733: Device reported enroll completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.733: Device reported finger status change: FP_FINGER_STATUS_NONE 126s (process:3837): libfprint-device-DEBUG: 20:25:34.733: Print for finger FP_FINGER_LEFT_INDEX enrolled 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.733: [egismoc] ENROLL_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.733: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.733: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.733: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.733: List 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.733: [egismoc] LIST_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.733: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.733: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.733: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.734: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.734: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.734: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.734: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.734: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.734: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.734: [egismoc] LIST_STATES entering state 1 126s (process:3837): libfprint-device-DEBUG: 20:25:34.734: Device reported listing completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.734: [egismoc] LIST_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.734: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.734: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.734: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-device-DEBUG: 20:25:34.735: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.735: Identify or Verify 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.735: [egismoc] IDENTIFY_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.735: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.735: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.735: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.735: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.736: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.736: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.736: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.736: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.736: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.736: [egismoc] IDENTIFY_STATES entering state 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.736: [egismoc] IDENTIFY_STATES entering state 2 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.736: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.736: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.736: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.736: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.737: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.737: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.737: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.737: [egismoc] IDENTIFY_STATES entering state 3 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.737: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.737: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.737: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.737: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.738: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.738: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.738: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.738: [egismoc] IDENTIFY_STATES entering state 4 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.738: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.738: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.739: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.739: [egismoc] IDENTIFY_STATES entering state 5 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.739: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.739: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.739: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.739: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.739: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.739: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.739: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.739: [egismoc] IDENTIFY_STATES entering state 6 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.739: Get check command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.739: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.739: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.739: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.740: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.740: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.740: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.741: Identify check callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.741: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.741: Identify successful for: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.741: Verifying against: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-device-DEBUG: 20:25:34.741: Device reported verify result 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.741: [egismoc] IDENTIFY_STATES entering state 7 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.741: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.741: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.741: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.741: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.741: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.742: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.742: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.742: [egismoc] IDENTIFY_STATES entering state 8 126s (process:3837): libfprint-device-DEBUG: 20:25:34.742: Device reported verify completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.742: Device reported finger status change: FP_FINGER_STATUS_NONE 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.742: [egismoc] IDENTIFY_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.742: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.742: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.742: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-device-DEBUG: 20:25:34.742: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.742: Identify or Verify 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.742: [egismoc] IDENTIFY_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.742: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.742: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.742: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.742: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.743: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.743: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.743: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.743: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.743: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.743: [egismoc] IDENTIFY_STATES entering state 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.743: [egismoc] IDENTIFY_STATES entering state 2 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.743: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.743: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.743: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.744: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.744: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.745: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.745: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.745: [egismoc] IDENTIFY_STATES entering state 3 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.745: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.745: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.745: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.745: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.746: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.746: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.746: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.746: [egismoc] IDENTIFY_STATES entering state 4 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.746: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.746: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.746: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.746: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.746: [egismoc] IDENTIFY_STATES entering state 5 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.746: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.746: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.746: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.747: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.747: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.747: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.747: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.747: [egismoc] IDENTIFY_STATES entering state 6 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.747: Get check command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.747: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.747: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.747: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.748: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.748: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.748: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.748: Identify check callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.748: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.748: Identify successful for: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-device-DEBUG: 20:25:34.748: Device reported identify result 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.748: [egismoc] IDENTIFY_STATES entering state 7 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.748: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.748: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.748: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.749: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.749: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.749: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.749: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.749: [egismoc] IDENTIFY_STATES entering state 8 126s (process:3837): libfprint-device-DEBUG: 20:25:34.749: Device reported identify completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.749: Device reported finger status change: FP_FINGER_STATUS_NONE 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.749: [egismoc] IDENTIFY_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.749: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.749: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.749: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-device-DEBUG: 20:25:34.750: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.750: Enroll 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.750: [egismoc] ENROLL_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.750: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.750: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.750: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.750: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.751: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.751: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.751: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.751: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.751: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.751: [egismoc] ENROLL_STATES entering state 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.751: [egismoc] ENROLL_STATES entering state 2 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.751: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.751: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.751: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.752: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.752: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.752: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.752: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.752: [egismoc] ENROLL_STATES entering state 3 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.752: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.752: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.752: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.753: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.753: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.753: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.753: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.753: [egismoc] ENROLL_STATES entering state 4 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.753: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.754: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.754: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.754: [egismoc] ENROLL_STATES entering state 5 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.754: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.754: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.754: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.754: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.755: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.755: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.755: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.755: [egismoc] ENROLL_STATES entering state 6 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.755: Get check command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.755: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.755: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.755: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.755: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.756: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.756: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.756: Enroll check callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.756: Response suffix valid: NO 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.756: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.756: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.756: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.756: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 126s (process:3837): libfprint-device-DEBUG: 20:25:34.756: Device reported enroll completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.756: Device reported finger status change: FP_FINGER_STATUS_NONE 126s (process:3837): libfprint-device-DEBUG: 20:25:34.756: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.756: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.756: List 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.756: [egismoc] LIST_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.756: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.756: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.756: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.757: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.757: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.757: [egismoc] LIST_STATES entering state 1 126s (process:3837): libfprint-device-DEBUG: 20:25:34.757: Device reported listing completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.757: [egismoc] LIST_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.757: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.757: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-device-DEBUG: 20:25:34.757: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: Enroll 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.757: [egismoc] ENROLL_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.757: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.757: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.758: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.758: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.758: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.759: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.759: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.759: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.759: [egismoc] ENROLL_STATES entering state 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.759: [egismoc] ENROLL_STATES entering state 2 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.759: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.759: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.759: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.759: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.760: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.760: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.760: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.760: [egismoc] ENROLL_STATES entering state 3 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.760: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.760: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.760: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.760: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.761: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.761: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.761: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.761: [egismoc] ENROLL_STATES entering state 4 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.761: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.761: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.761: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.761: [egismoc] ENROLL_STATES entering state 5 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.761: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.761: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.761: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.762: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.762: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.762: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.762: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.762: [egismoc] ENROLL_STATES entering state 6 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.762: Get check command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.762: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.762: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.762: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.763: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.763: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.763: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.763: Enroll check callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.763: Response suffix valid: yes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.763: [egismoc] ENROLL_STATES entering state 7 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.763: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.763: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.763: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.764: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.764: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.764: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.764: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.764: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.764: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.764: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.764: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.765: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.765: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.765: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.765: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.765: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.765: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.765: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.765: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.766: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.767: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.767: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.767: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.767: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.767: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.767: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.768: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.768: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.768: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.768: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.768: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.768: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.768: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.768: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.768: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.768: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.768: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.768: Partial capture successful. Please touch the sensor again (1/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.768: Device reported enroll progress, reported 1 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.769: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.769: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.769: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.769: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.769: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.769: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.769: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.769: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.769: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.769: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.769: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.769: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.770: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.771: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.771: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.771: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.771: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.771: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.771: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.771: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.771: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.771: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.771: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.771: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.771: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.772: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.772: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.772: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.772: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.772: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.772: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.772: Partial capture successful. Please touch the sensor again (2/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.772: Device reported enroll progress, reported 2 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.772: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.772: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.772: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.772: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.773: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.773: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.773: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.773: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.773: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.773: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.773: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.773: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.774: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.774: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.774: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.774: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.774: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.774: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.774: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.775: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.775: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.775: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.775: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.775: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.775: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.775: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.776: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Response suffix valid: NO 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Response suffix valid: yes 126s (process:3837): libfprint-device-DEBUG: 20:25:34.776: Device reported enroll progress, reported 2 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.776: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.776: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.776: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.776: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.777: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.777: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.777: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.777: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.777: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.777: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.777: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.777: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.778: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.778: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.778: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.778: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.778: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.778: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.778: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.778: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.778: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.778: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.778: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.779: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.779: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Response suffix valid: NO 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Response suffix valid: yes 126s (process:3837): libfprint-device-DEBUG: 20:25:34.779: Device reported enroll progress, reported 2 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.779: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.779: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.779: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.780: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.780: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.780: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.780: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.780: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.780: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.780: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.780: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.781: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.781: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.781: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.781: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.781: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.781: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.782: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.782: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.782: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.782: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.782: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.782: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.782: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.783: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.783: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.783: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.783: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.783: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.783: Partial capture successful. Please touch the sensor again (3/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.783: Device reported enroll progress, reported 3 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.783: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.783: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.783: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.783: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.783: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.784: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.784: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.784: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.784: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.784: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.784: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.784: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.784: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.785: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.785: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.785: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.785: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.785: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.785: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.785: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.785: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.785: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.785: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.785: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.785: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.786: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.786: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Response suffix valid: NO 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Response suffix valid: yes 126s (process:3837): libfprint-device-DEBUG: 20:25:34.786: Device reported enroll progress, reported 3 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.786: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.786: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.786: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.787: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.787: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.788: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.788: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.788: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.788: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.788: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.788: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.788: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.789: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.789: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.789: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.789: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.789: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.789: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.789: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.789: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.789: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.789: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.789: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.789: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.790: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.790: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.790: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.790: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.790: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.790: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.790: Partial capture successful. Please touch the sensor again (4/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.790: Device reported enroll progress, reported 4 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.790: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.790: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.790: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.790: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.791: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.791: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.791: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.791: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.791: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.791: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.791: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.791: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.792: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.792: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.792: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.792: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.792: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.792: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.792: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.793: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.793: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.793: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.793: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.793: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.793: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.794: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.794: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.794: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.794: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.794: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.794: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.794: Partial capture successful. Please touch the sensor again (5/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.794: Device reported enroll progress, reported 5 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.794: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.794: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.794: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.794: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.795: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.795: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.795: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.795: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.795: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.795: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.795: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.795: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.796: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.796: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.796: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.796: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.796: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.796: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.797: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.797: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.797: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.797: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.797: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.797: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.798: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.798: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.798: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.798: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.798: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.798: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.798: Partial capture successful. Please touch the sensor again (6/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.798: Device reported enroll progress, reported 6 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.798: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.798: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.798: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.798: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.799: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.799: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.799: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.799: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.799: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.799: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.799: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.799: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.800: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.800: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.800: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.800: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.800: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.800: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.800: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.801: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.801: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.801: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.801: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.801: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.801: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.801: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.802: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.802: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.802: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.802: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.802: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.802: Partial capture successful. Please touch the sensor again (7/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.802: Device reported enroll progress, reported 7 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.802: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.802: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.802: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.802: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.803: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.803: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.803: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.804: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.804: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.804: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.804: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.804: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.804: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.805: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.805: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.805: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.805: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.805: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.805: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.805: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.805: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.805: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.805: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.805: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.806: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.807: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.807: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.807: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.807: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.807: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.807: Partial capture successful. Please touch the sensor again (8/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.807: Device reported enroll progress, reported 8 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.807: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.807: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.807: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.807: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.807: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.808: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.808: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.808: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.808: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.808: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.808: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.808: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.808: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.809: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.809: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.809: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.809: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.809: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.810: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.810: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.810: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.810: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.810: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.810: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.810: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.811: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.811: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.811: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.811: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.811: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.811: Partial capture successful. Please touch the sensor again (9/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.811: Device reported enroll progress, reported 9 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.811: [egismoc] ENROLL_STATES entering state 8 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.811: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.811: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.811: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.811: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.812: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.812: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.812: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.812: [egismoc] ENROLL_STATES entering state 9 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.812: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.812: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.812: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.812: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.813: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.813: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.813: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.813: [egismoc] ENROLL_STATES entering state 10 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.813: Wait for finger on sensor 126s (process:3837): libfprint-device-DEBUG: 20:25:34.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.813: Finger on sensor callback 126s (process:3837): libfprint-device-DEBUG: 20:25:34.813: Device reported finger status change: FP_FINGER_STATUS_PRESENT 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.813: [egismoc] ENROLL_STATES entering state 11 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.813: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.813: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.813: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.814: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.814: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.814: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.814: Read capture callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.814: Response prefix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.814: Response suffix valid: yes 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.814: Partial capture successful. Please touch the sensor again (10/10) 126s (process:3837): libfprint-device-DEBUG: 20:25:34.814: Device reported enroll progress, reported 10 of 10 have been completed 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.814: [egismoc] ENROLL_STATES entering state 12 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.814: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.814: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.814: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.815: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.815: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.816: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.816: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.816: [egismoc] ENROLL_STATES entering state 13 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.816: New fingerprint ID: FP1-00000000-7-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.816: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.816: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.816: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.816: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.817: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.817: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.817: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.817: [egismoc] ENROLL_STATES entering state 14 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.817: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.817: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.817: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.817: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.818: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.818: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.818: Task SSM next state callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.818: [egismoc] ENROLL_STATES entering state 15 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.818: Enrollment was successful! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.818: Device reported enroll completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.818: Device reported finger status change: FP_FINGER_STATUS_NONE 126s (process:3837): libfprint-device-DEBUG: 20:25:34.818: Print for finger FP_FINGER_RIGHT_INDEX enrolled 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.818: [egismoc] ENROLL_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.818: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.818: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.818: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.818: List 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.818: [egismoc] LIST_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.818: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.818: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.818: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.819: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.819: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.819: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.819: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.820: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.820: Device fingerprint 2: FP1-00000000-7-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.820: Number of currently enrolled fingerprints on the device is 2 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.820: [egismoc] LIST_STATES entering state 1 126s (process:3837): libfprint-device-DEBUG: 20:25:34.820: Device reported listing completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.820: [egismoc] LIST_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.820: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.820: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.820: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.820: Delete 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.820: [egismoc] DELETE_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.820: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.820: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.820: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.820: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.821: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Device fingerprint 1: FP1-00000000-2-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Device fingerprint 2: FP1-00000000-7-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Number of currently enrolled fingerprints on the device is 2 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.821: [egismoc] DELETE_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Get delete command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.821: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.821: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.822: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.822: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.822: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.822: Delete callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.822: Response prefix valid: yes 126s (process:3837): libfprint-device-DEBUG: 20:25:34.822: Device reported deletion completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.823: [egismoc] DELETE_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.823: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.823: Completing action FPI_DEVICE_ACTION_DELETE in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.823: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.823: List 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.823: [egismoc] LIST_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.823: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.823: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.823: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.823: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.824: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: Device fingerprint 1: FP1-00000000-7-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.824: [egismoc] LIST_STATES entering state 1 126s (process:3837): libfprint-device-DEBUG: 20:25:34.824: Device reported listing completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.824: [egismoc] LIST_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.824: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.824: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: Clear storage 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.824: [egismoc] DELETE_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.824: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.824: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.825: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.825: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.825: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.825: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.825: Device fingerprint 1: FP1-00000000-7-00000000-nobody 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.825: Number of currently enrolled fingerprints on the device is 1 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.825: [egismoc] DELETE_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.825: Get delete command 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.825: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.825: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.825: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.826: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.826: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.827: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.827: Delete callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.827: Response prefix valid: yes 126s (process:3837): libfprint-device-DEBUG: 20:25:34.827: Device reported deletion completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.827: [egismoc] DELETE_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.827: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.827: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.827: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.827: List 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.827: [egismoc] LIST_STATES entering state 0 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.827: Execute command and get response 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.827: Get check bytes 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.827: [egismoc] CMD_STATES entering state 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.827: [egismoc] CMD_STATES entering state 1 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.828: Command receive callback 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.828: [egismoc] CMD_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.828: List callback 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.828: Number of currently enrolled fingerprints on the device is 0 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.828: [egismoc] LIST_STATES entering state 1 126s (process:3837): libfprint-device-DEBUG: 20:25:34.828: Device reported listing completion 126s (process:3837): libfprint-SSM-DEBUG: 20:25:34.828: [egismoc] LIST_STATES completed successfully 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.828: Task SSM done 126s (process:3837): libfprint-device-DEBUG: 20:25:34.828: Completing action FPI_DEVICE_ACTION_LIST in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.828: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.828: Closing device 126s (process:3837): libfprint-egismoc-DEBUG: 20:25:34.828: Cancel 126s (process:3837): libfprint-device-DEBUG: 20:25:34.828: Device reported close completion 126s (process:3837): libfprint-device-DEBUG: 20:25:34.829: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 126s (process:3837): libfprint-device-DEBUG: 20:25:34.829: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 126s listing - device should have prints 126s clear device storage 126s clear done 126s listing - device should be empty 126s enrolling 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 1, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 2, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 3, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 4, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 5, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 6, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 7, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 8, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 9, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 10, , None, None) 126s enroll done 126s listing - device should have 1 print 126s verifying 126s verify done 126s async identifying 126s indentification_done: 126s try to enroll duplicate 126s duplicate enroll attempt done 126s listing - device should still only have 1 print 126s enroll new finger 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 1, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 2, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 3, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 4, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 5, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 6, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 7, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 8, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 9, , None, None) 126s finger status: 126s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7caddcce2400 (FpiDeviceEgisMoc at 0x3057f950)>, 10, , None, None) 126s enroll new finger done 126s listing - device should have 2 prints 126s deleting first print 126s delete done 126s listing - device should only have second print 126s clear device storage 126s clear done 126s listing - device should be empty 126s ** (umockdev-run:3833): DEBUG: 20:25:34.849: umockdev.vala:154: Removing test bed /tmp/umockdev.A1XA22 126s (umockdev-run:3833): GLib-DEBUG: 20:25:34.855: unsetenv() is not thread-safe and should not be used after threads are created 126s PASS: libfprint-2/driver-egismoc-05a1.test 126s Running test: libfprint-2/driver-vfs0050.test 126s ** (umockdev-run:3845): DEBUG: 20:25:34.898: umockdev.vala:127: Created udev test bed /tmp/umockdev.RZCI22 126s ** (umockdev-run:3845): DEBUG: 20:25:34.898: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 126s ** (umockdev-run:3845): DEBUG: 20:25:34.899: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 126s ** (umockdev-run:3845): DEBUG: 20:25:34.903: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RZCI22/dev/bus/usb/001/004 126s ** (umockdev-run:3845): DEBUG: 20:25:34.903: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 126s ** (umockdev-run:3845): DEBUG: 20:25:34.904: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 126s ** (umockdev-run:3845): DEBUG: 20:25:34.907: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RZCI22/dev/bus/usb/001/001 126s ** (umockdev-run:3845): DEBUG: 20:25:34.907: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 126s ** (umockdev-run:3845): DEBUG: 20:25:34.907: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 126s (umockdev-run:3845): GLib-GIO-DEBUG: 20:25:34.910: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 127s (process:3849): libfprint-context-DEBUG: 20:25:35.011: Initializing FpContext (libfprint version 1.94.8+tod1) 127s (process:3849): libfprint-tod-DEBUG: 20:25:35.011: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 127s (process:3849): libfprint-context-DEBUG: 20:25:35.013: No driver found for USB device 1D6B:0002 127s (process:3849): libfprint-device-DEBUG: 20:25:35.013: Device reported probe completion 127s (process:3849): libfprint-device-DEBUG: 20:25:35.014: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s (process:3849): libfprint-device-DEBUG: 20:25:35.014: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.015: [vfs0050] SSM_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.016: [vfs0050] SSM_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.016: [vfs0050] SSM_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.017: [vfs0050] SSM_STATES entering state 3 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.017: [vfs0050] SUBSM1_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.017: [vfs0050] SUBSM1_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.018: [vfs0050] SUBSM1_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.019: [vfs0050] SUBSM1_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.019: [vfs0050] SSM_STATES entering state 4 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.019: [vfs0050] SUBSM2_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.019: [vfs0050] SUBSM2_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.020: [vfs0050] SUBSM2_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.021: [vfs0050] SUBSM2_STATES entering state 3 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.021: [vfs0050] SUBSM2_STATES entering state 4 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.022: [vfs0050] SUBSM2_STATES entering state 5 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.022: [vfs0050] SUBSM2_STATES entering state 6 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.023: [vfs0050] SUBSM1_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.023: [vfs0050] SUBSM1_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.024: [vfs0050] SUBSM1_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.024: [vfs0050] SUBSM1_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.024: [vfs0050] SUBSM2_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.024: [vfs0050] SSM_STATES entering state 5 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.024: [vfs0050] SSM_STATES completed successfully 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.024: Image device open completed 127s (process:3849): libfprint-device-DEBUG: 20:25:35.024: Device reported open completion 127s (process:3849): libfprint-device-DEBUG: 20:25:35.024: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s (process:3849): libfprint-device-DEBUG: 20:25:35.024: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (process:3849): libfprint-device-DEBUG: 20:25:35.025: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.025: Activating image device 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.025: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.025: [vfs0050] SSM_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.025: [vfs0050] SSM_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.026: [vfs0050] SSM_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.026: [vfs0050] SSM_STATES entering state 3 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.027: [vfs0050] SUBSM1_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.027: [vfs0050] SUBSM1_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.028: [vfs0050] SUBSM1_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.029: [vfs0050] SUBSM1_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.029: [vfs0050] SSM_STATES entering state 4 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.029: [vfs0050] SUBSM2_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.029: [vfs0050] SUBSM2_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.030: [vfs0050] SUBSM2_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.030: [vfs0050] SUBSM2_STATES entering state 3 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.031: [vfs0050] SUBSM2_STATES entering state 4 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.031: [vfs0050] SUBSM2_STATES entering state 5 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.032: [vfs0050] SUBSM2_STATES entering state 6 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.032: [vfs0050] SUBSM1_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.032: [vfs0050] SUBSM1_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.033: [vfs0050] SUBSM1_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.033: [vfs0050] SUBSM1_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.033: [vfs0050] SUBSM2_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.033: [vfs0050] SSM_STATES entering state 5 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.033: [vfs0050] SUBSM2_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.034: [vfs0050] SUBSM2_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.034: [vfs0050] SUBSM2_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.035: [vfs0050] SUBSM2_STATES entering state 3 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.035: [vfs0050] SUBSM2_STATES entering state 4 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.036: [vfs0050] SUBSM2_STATES entering state 5 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.036: [vfs0050] SUBSM2_STATES entering state 6 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.036: [vfs0050] SUBSM2_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.036: [vfs0050] SSM_STATES entering state 6 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.036: Image device activation completed 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.036: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.036: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 127s (process:3849): libfprint-device-DEBUG: 20:25:35.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.036: [vfs0050] SSM_STATES entering state 7 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.037: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-device-DEBUG: 20:25:35.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.037: Image device reported finger status: on 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.037: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.038: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.039: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.039: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.040: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.040: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.041: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.042: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.043: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.043: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.044: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.045: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.045: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.046: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.047: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.047: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.048: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.049: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.049: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.050: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.051: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.051: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.052: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.053: [vfs0050] SSM_STATES entering state 8 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.053: [vfs0050] SSM_STATES entering state 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 1739651135053741 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.053: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 91 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 85 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 85 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.054: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 48 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 48 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.055: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 91 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.056: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.057: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.058: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 74 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.059: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 76 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 74 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 48 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 76 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.060: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 85 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 74 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 48 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 85 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 80 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 74 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 72 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 91 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 91 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 76 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 72 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 80 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 76 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 74 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 74 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 100 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 3 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.061: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 2 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.062: 1 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: offsets_filtered: 1739651135063193 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 5 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.063: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.064: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 99 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 98 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 97 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 96 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 95 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 93 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 91 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 88 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 86 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 85 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 85 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 84 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 79 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 75 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 48 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.065: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 30 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.066: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 19 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 18 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 16 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.067: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 11 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 12 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 64 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 48 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 94 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 92 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 90 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 89 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 87 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 83 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 81 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 77 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 70 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 20 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 24 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 60 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 54 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 43 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 42 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 36 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 47 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 46 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 32 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 26 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 23 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 25 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 62 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 56 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 49 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 44 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 37 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 38 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 52 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 73 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 71 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 69 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 68 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 67 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 66 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 61 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 59 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 57 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 51 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 33 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 34 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 65 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 63 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 58 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 55 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 50 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 53 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 45 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 41 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 40 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 39 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 35 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 31 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 29 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 28 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 27 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 22 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 21 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 17 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 15 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 14 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 13 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 10 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 9 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 8 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 7 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 4 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 6 127s (process:3849): libfprint-assembling-DEBUG: 20:25:35.068: 1 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.069: Image device captured an image 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.070: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 127s (process:3849): libfprint-device-DEBUG: 20:25:35.070: Device reported finger status change: FP_FINGER_STATUS_PRESENT 127s (process:3849): libfprint-device-DEBUG: 20:25:35.070: Device reported finger status change: FP_FINGER_STATUS_NONE 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.070: Image device reported finger status: off 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.070: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.070: Deactivating image device 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.070: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 127s (process:3849): libfprint-image-DEBUG: 20:25:35.093: Minutiae scan completed in 0.023513 secs 127s (process:3849): libfprint-device-DEBUG: 20:25:35.126: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.153: [vfs0050] SSM_STATES entering state 10 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.153: [vfs0050] SSM_STATES entering state 3 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.153: [vfs0050] SUBSM1_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.154: [vfs0050] SUBSM1_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.154: [vfs0050] SUBSM1_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.155: [vfs0050] SUBSM1_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.155: [vfs0050] SSM_STATES entering state 4 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.155: [vfs0050] SUBSM2_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.156: [vfs0050] SUBSM2_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.156: [vfs0050] SUBSM2_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.157: [vfs0050] SUBSM2_STATES entering state 3 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.157: [vfs0050] SUBSM2_STATES entering state 4 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.158: [vfs0050] SUBSM2_STATES entering state 5 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.158: [vfs0050] SUBSM2_STATES entering state 6 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.158: [vfs0050] SUBSM1_STATES entering state 0 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.159: [vfs0050] SUBSM1_STATES entering state 1 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.159: [vfs0050] SUBSM1_STATES entering state 2 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.160: [vfs0050] SUBSM1_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.160: [vfs0050] SUBSM2_STATES completed successfully 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.160: [vfs0050] SSM_STATES entering state 5 127s (process:3849): libfprint-SSM-DEBUG: 20:25:35.160: [vfs0050] SSM_STATES completed successfully 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.160: Image device deactivation completed 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.160: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 127s (process:3849): libfprint-device-DEBUG: 20:25:35.160: Device reported capture completion 127s (process:3849): libfprint-device-DEBUG: 20:25:35.160: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 127s (process:3849): libfprint-device-DEBUG: 20:25:35.160: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s (process:3849): libfprint-image_device-DEBUG: 20:25:35.160: Image device close completed 127s (process:3849): libfprint-device-DEBUG: 20:25:35.160: Device reported close completion 127s (process:3849): libfprint-device-DEBUG: 20:25:35.160: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s (process:3849): libfprint-device-DEBUG: 20:25:35.160: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ** (umockdev-run:3845): DEBUG: 20:25:35.302: umockdev.vala:154: Removing test bed /tmp/umockdev.RZCI22 127s (umockdev-run:3845): GLib-DEBUG: 20:25:35.308: unsetenv() is not thread-safe and should not be used after threads are created 127s Comparing PNGs /tmp/libfprint-umockdev-test-cudsfu30/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 127s PASS: libfprint-2/driver-vfs0050.test 127s Running test: libfprint-2/driver-vfs5011.test 127s ** (umockdev-run:3858): DEBUG: 20:25:35.383: umockdev.vala:127: Created udev test bed /tmp/umockdev.TQY612 127s ** (umockdev-run:3858): DEBUG: 20:25:35.383: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 127s ** (umockdev-run:3858): DEBUG: 20:25:35.384: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 127s ** (umockdev-run:3858): DEBUG: 20:25:35.388: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TQY612/dev/bus/usb/002/017 127s ** (umockdev-run:3858): DEBUG: 20:25:35.388: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 127s ** (umockdev-run:3858): DEBUG: 20:25:35.388: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 127s ** (umockdev-run:3858): DEBUG: 20:25:35.391: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TQY612/dev/bus/usb/002/001 127s ** (umockdev-run:3858): DEBUG: 20:25:35.391: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 127s ** (umockdev-run:3858): DEBUG: 20:25:35.392: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 127s (umockdev-run:3858): GLib-GIO-DEBUG: 20:25:35.394: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 127s (process:3862): libfprint-context-DEBUG: 20:25:35.485: Initializing FpContext (libfprint version 1.94.8+tod1) 127s (process:3862): libfprint-tod-DEBUG: 20:25:35.485: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 127s (process:3862): libfprint-context-DEBUG: 20:25:35.487: No driver found for USB device 1D6B:0002 127s (process:3862): libfprint-device-DEBUG: 20:25:35.488: Device reported probe completion 127s (process:3862): libfprint-device-DEBUG: 20:25:35.488: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s (process:3862): libfprint-device-DEBUG: 20:25:35.488: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.489: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.489: [vfs5011] DEVICE OPEN entering state 0 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.490: Sending vfs5011_cmd_01 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.490: [vfs5011] DEVICE OPEN entering state 1 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.490: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.491: Got 38 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.491: [vfs5011] DEVICE OPEN entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.491: Sending vfs5011_cmd_19 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.491: [vfs5011] DEVICE OPEN entering state 3 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.491: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.492: Got 64 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.492: [vfs5011] DEVICE OPEN entering state 4 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.492: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.493: Got 4 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.493: [vfs5011] DEVICE OPEN entering state 5 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.493: Sending vfs5011_init_00 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.493: [vfs5011] DEVICE OPEN entering state 6 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.493: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.494: Got 6 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.494: [vfs5011] DEVICE OPEN entering state 7 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.494: Sending vfs5011_init_01 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.494: [vfs5011] DEVICE OPEN entering state 8 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.494: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.495: Got 7 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.495: [vfs5011] DEVICE OPEN entering state 9 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.495: Sending vfs5011_init_02 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.495: [vfs5011] DEVICE OPEN entering state 10 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.495: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.496: [vfs5011] DEVICE OPEN entering state 11 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.496: Sending vfs5011_cmd_01 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.497: [vfs5011] DEVICE OPEN entering state 12 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.497: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.497: Got 38 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.497: [vfs5011] DEVICE OPEN entering state 13 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.497: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.498: [vfs5011] DEVICE OPEN entering state 14 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.498: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.498: [vfs5011] DEVICE OPEN entering state 15 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.498: Sending vfs5011_init_03 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.499: [vfs5011] DEVICE OPEN entering state 16 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.499: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.500: [vfs5011] DEVICE OPEN entering state 17 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.500: Sending vfs5011_init_04 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.500: [vfs5011] DEVICE OPEN entering state 18 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.500: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.501: [vfs5011] DEVICE OPEN entering state 19 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.501: Receiving 256 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.501: Got 256 bytes out of 256 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.501: [vfs5011] DEVICE OPEN entering state 20 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.502: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.502: Got 32 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.502: [vfs5011] DEVICE OPEN entering state 21 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.502: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.503: [vfs5011] DEVICE OPEN entering state 22 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.503: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.503: [vfs5011] DEVICE OPEN entering state 23 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.503: Sending vfs5011_init_05 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.504: [vfs5011] DEVICE OPEN entering state 24 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.504: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.504: [vfs5011] DEVICE OPEN entering state 25 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.504: Sending vfs5011_cmd_01 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.505: [vfs5011] DEVICE OPEN entering state 26 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.505: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.505: Got 38 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.506: [vfs5011] DEVICE OPEN entering state 27 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.506: Sending vfs5011_init_06 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.506: [vfs5011] DEVICE OPEN entering state 28 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.506: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.507: [vfs5011] DEVICE OPEN entering state 29 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.507: Receiving 17216 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.507: Got 17216 bytes out of 17216 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.507: [vfs5011] DEVICE OPEN entering state 30 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.507: Receiving 32 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.508: Got 32 bytes out of 32 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.508: [vfs5011] DEVICE OPEN entering state 31 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.508: Sending vfs5011_init_07 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.508: [vfs5011] DEVICE OPEN entering state 32 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.508: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.509: [vfs5011] DEVICE OPEN entering state 33 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.509: Receiving 45056 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.509: Got 45056 bytes out of 45056 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.509: [vfs5011] DEVICE OPEN entering state 34 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.509: Sending vfs5011_init_08 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.510: [vfs5011] DEVICE OPEN entering state 35 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.510: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.511: [vfs5011] DEVICE OPEN entering state 36 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.511: Receiving 16896 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.511: Got 16896 bytes out of 16896 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.511: [vfs5011] DEVICE OPEN entering state 37 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.511: Sending vfs5011_init_09 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.512: [vfs5011] DEVICE OPEN entering state 38 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.512: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.512: [vfs5011] DEVICE OPEN entering state 39 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.512: Receiving 4928 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.513: Got 4928 bytes out of 4928 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.513: [vfs5011] DEVICE OPEN entering state 40 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.513: Sending vfs5011_init_10 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.514: [vfs5011] DEVICE OPEN entering state 41 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.514: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.514: [vfs5011] DEVICE OPEN entering state 42 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.514: Receiving 5632 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.515: Got 5632 bytes out of 5632 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.515: [vfs5011] DEVICE OPEN entering state 43 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.515: Sending vfs5011_init_11 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.515: [vfs5011] DEVICE OPEN entering state 44 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.515: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.516: [vfs5011] DEVICE OPEN entering state 45 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.516: Receiving 5632 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.516: Got 5632 bytes out of 5632 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.516: [vfs5011] DEVICE OPEN entering state 46 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.516: Sending vfs5011_init_12 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.517: [vfs5011] DEVICE OPEN entering state 47 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.517: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.517: [vfs5011] DEVICE OPEN entering state 48 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.517: Receiving 3328 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.518: Got 3328 bytes out of 3328 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.518: [vfs5011] DEVICE OPEN entering state 49 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.518: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.518: Got 32 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.518: [vfs5011] DEVICE OPEN entering state 50 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.518: Sending vfs5011_init_13 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.519: [vfs5011] DEVICE OPEN entering state 51 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.519: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.520: [vfs5011] DEVICE OPEN entering state 52 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.520: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.520: [vfs5011] DEVICE OPEN entering state 53 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.520: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.521: [vfs5011] DEVICE OPEN entering state 54 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.521: Sending vfs5011_init_03 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.521: [vfs5011] DEVICE OPEN entering state 55 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.521: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.522: [vfs5011] DEVICE OPEN entering state 56 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.522: Sending vfs5011_init_14 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.522: [vfs5011] DEVICE OPEN entering state 57 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.523: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.523: [vfs5011] DEVICE OPEN entering state 58 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.523: Receiving 4800 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.524: Got 4800 bytes out of 4800 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.524: [vfs5011] DEVICE OPEN entering state 59 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.524: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.524: [vfs5011] DEVICE OPEN entering state 60 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.524: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.525: [vfs5011] DEVICE OPEN entering state 61 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.525: Sending vfs5011_init_02 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.525: [vfs5011] DEVICE OPEN entering state 62 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.525: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.526: [vfs5011] DEVICE OPEN entering state 63 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.526: Sending vfs5011_cmd_27 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.526: [vfs5011] DEVICE OPEN entering state 64 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.527: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.527: Got 22 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.527: [vfs5011] DEVICE OPEN entering state 65 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.527: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.528: [vfs5011] DEVICE OPEN entering state 66 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.528: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.528: [vfs5011] DEVICE OPEN entering state 67 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.528: Sending vfs5011_init_15 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.529: [vfs5011] DEVICE OPEN entering state 68 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.529: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.529: [vfs5011] DEVICE OPEN entering state 69 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.529: Sending vfs5011_init_16 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.530: [vfs5011] DEVICE OPEN entering state 70 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.530: Receiving 2368 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.530: Got 2368 bytes out of 2368 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.530: [vfs5011] DEVICE OPEN entering state 71 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.530: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.531: Got 36 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.531: [vfs5011] DEVICE OPEN entering state 72 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.531: Receiving 4800 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.532: Got 4800 bytes out of 4800 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.532: [vfs5011] DEVICE OPEN entering state 73 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.532: Sending vfs5011_init_17 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.532: [vfs5011] DEVICE OPEN entering state 74 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.532: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.534: [vfs5011] DEVICE OPEN entering state 75 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.534: Sending vfs5011_init_18 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.536: [vfs5011] DEVICE OPEN entering state 76 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.536: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.536: [vfs5011] DEVICE OPEN completed successfully 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.536: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.536: Image device open completed 127s (process:3862): libfprint-device-DEBUG: 20:25:35.536: Device reported open completion 127s (process:3862): libfprint-device-DEBUG: 20:25:35.536: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s (process:3862): libfprint-device-DEBUG: 20:25:35.536: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (process:3862): libfprint-device-DEBUG: 20:25:35.537: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.537: Activating image device 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.537: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.537: device initialized 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.537: creating ssm 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.537: starting ssm 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.537: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.537: main_loop: state 0 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.537: [vfs5011] ACTIVATE REQUEST entering state 0 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.537: Sending vfs5011_cmd_04 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.537: ssm done, getting out 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.537: [vfs5011] ACTIVATE REQUEST entering state 1 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.537: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.538: Got 64 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.538: [vfs5011] ACTIVATE REQUEST entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.538: Receiving 84032 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.539: Got 176 bytes out of 84032 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.539: [vfs5011] ACTIVATE REQUEST entering state 3 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.539: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.539: [vfs5011] ACTIVATE REQUEST entering state 4 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.539: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.540: [vfs5011] ACTIVATE REQUEST entering state 5 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.540: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.540: [vfs5011] ACTIVATE REQUEST entering state 6 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.540: Sending vfs5011_prepare_00 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.541: [vfs5011] ACTIVATE REQUEST entering state 7 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.541: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.541: [vfs5011] ACTIVATE REQUEST entering state 8 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.541: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.542: [vfs5011] ACTIVATE REQUEST entering state 9 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.542: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.542: [vfs5011] ACTIVATE REQUEST entering state 10 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.542: Sending vfs5011_prepare_01 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.543: [vfs5011] ACTIVATE REQUEST entering state 11 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.543: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.543: [vfs5011] ACTIVATE REQUEST entering state 12 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.543: Sending vfs5011_prepare_02 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.544: [vfs5011] ACTIVATE REQUEST entering state 13 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.544: Receiving 2368 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.544: Got 2368 bytes out of 2368 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.544: [vfs5011] ACTIVATE REQUEST entering state 14 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.544: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.545: Got 36 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.545: [vfs5011] ACTIVATE REQUEST entering state 15 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.545: Receiving 4800 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.545: Got 4800 bytes out of 4800 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.546: [vfs5011] ACTIVATE REQUEST entering state 16 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.546: Sending vfs5011_prepare_03 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.546: [vfs5011] ACTIVATE REQUEST entering state 17 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.546: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.546: [vfs5011] ACTIVATE REQUEST entering state 18 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.546: Sending vfs5011_prepare_04 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.547: [vfs5011] ACTIVATE REQUEST entering state 19 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.547: Receiving 2368 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.547: [vfs5011] ACTIVATE REQUEST completed successfully 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.547: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.547: main_loop: state 1 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.547: capture_init 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.547: Image device activation completed 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 127s (process:3862): libfprint-device-DEBUG: 20:25:35.547: Device reported finger status change: FP_FINGER_STATUS_NEEDED 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.547: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.547: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.547: capture_chunk_async: capture 256 lines, already have 0 127s (process:3862): libfprint-device-DEBUG: 20:25:35.548: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.548: Image device reported finger status: on 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.548: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.548: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.548: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.548: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.548: capture_chunk_async: capture 256 lines, already have 6 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.549: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.549: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.549: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.549: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.549: capture_chunk_async: capture 256 lines, already have 25 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.550: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.550: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.550: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.550: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.550: capture_chunk_async: capture 256 lines, already have 54 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.551: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.551: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.551: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.551: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.551: capture_chunk_async: capture 256 lines, already have 89 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.551: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.552: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.552: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.552: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.552: capture_chunk_async: capture 256 lines, already have 117 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.552: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.552: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.553: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.553: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.553: capture_chunk_async: capture 256 lines, already have 144 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.554: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.554: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.554: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.554: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.554: capture_chunk_async: capture 256 lines, already have 180 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.555: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.555: process_chunk: got 61440 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.555: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.555: main_loop: state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.555: capture_chunk_async: capture 256 lines, already have 273 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.556: Image device reported finger status: on 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.556: process_chunk: got 61440 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.556: process_chunk: got 50 empty lines, finishing 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.556: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.556: main_loop: state 3 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.557: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.557: main_loop: state 4 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.557: [vfs5011] PREPARE CAPTURE entering state 0 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.557: Sending vfs5011_cmd_04 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.558: [vfs5011] PREPARE CAPTURE entering state 1 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.558: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.558: Got 64 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.558: [vfs5011] PREPARE CAPTURE entering state 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.558: Receiving 84032 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.559: Got 176 bytes out of 84032 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.559: [vfs5011] PREPARE CAPTURE entering state 3 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.559: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.559: [vfs5011] PREPARE CAPTURE entering state 4 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.559: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.560: [vfs5011] PREPARE CAPTURE entering state 5 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.560: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.561: [vfs5011] PREPARE CAPTURE entering state 6 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.561: Sending vfs5011_prepare_00 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.562: [vfs5011] PREPARE CAPTURE entering state 7 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.562: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.563: [vfs5011] PREPARE CAPTURE entering state 8 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.563: Sending vfs5011_cmd_1A 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.563: [vfs5011] PREPARE CAPTURE entering state 9 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.563: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.564: [vfs5011] PREPARE CAPTURE entering state 10 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.564: Sending vfs5011_prepare_01 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.564: [vfs5011] PREPARE CAPTURE entering state 11 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.564: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.565: [vfs5011] PREPARE CAPTURE entering state 12 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.565: Sending vfs5011_prepare_02 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.565: [vfs5011] PREPARE CAPTURE entering state 13 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.565: Receiving 2368 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.566: Got 2368 bytes out of 2368 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.566: [vfs5011] PREPARE CAPTURE entering state 14 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.566: Receiving 64 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.566: Got 36 bytes out of 64 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.566: [vfs5011] PREPARE CAPTURE entering state 15 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.566: Receiving 4800 bytes 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.567: Got 4800 bytes out of 4800 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.567: [vfs5011] PREPARE CAPTURE entering state 16 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.567: Sending vfs5011_prepare_03 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.567: [vfs5011] PREPARE CAPTURE entering state 17 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.568: Receiving 64 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.568: [vfs5011] PREPARE CAPTURE entering state 18 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.568: Sending vfs5011_prepare_04 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.569: [vfs5011] PREPARE CAPTURE entering state 19 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.569: Receiving 2368 bytes 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.569: [vfs5011] PREPARE CAPTURE completed successfully 127s (process:3862): libfprint-SSM-DEBUG: 20:25:35.569: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.569: finishing 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 1739651135569677 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 1 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 4 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 4 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 3 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 3 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 4 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 4 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 4 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 11 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 30 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.569: 26 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 4 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 2 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: offsets_filtered: 1739651135570150 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 5 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 27 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 29 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 28 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 6 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 9 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 8 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 7 127s (process:3862): libfprint-assembling-DEBUG: 20:25:35.570: 2 127s (process:3862): libfprint-vfs5011-DEBUG: 20:25:35.570: Image captured, committing 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.570: Image device captured an image 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.571: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 127s (process:3862): libfprint-device-DEBUG: 20:25:35.571: Device reported finger status change: FP_FINGER_STATUS_PRESENT 127s (process:3862): libfprint-device-DEBUG: 20:25:35.571: Device reported finger status change: FP_FINGER_STATUS_NONE 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.571: Image device reported finger status: off 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.571: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.571: Deactivating image device 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.571: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.571: Image device deactivation completed 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.571: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 127s (process:3862): libfprint-image-DEBUG: 20:25:35.581: Minutiae scan completed in 0.009621 secs 127s (process:3862): libfprint-device-DEBUG: 20:25:35.581: Device reported capture completion 127s (process:3862): libfprint-device-DEBUG: 20:25:35.581: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 127s (process:3862): libfprint-device-DEBUG: 20:25:35.581: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s (process:3862): libfprint-image_device-DEBUG: 20:25:35.582: Image device close completed 127s (process:3862): libfprint-device-DEBUG: 20:25:35.582: Device reported close completion 127s (process:3862): libfprint-device-DEBUG: 20:25:35.582: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s (process:3862): libfprint-device-DEBUG: 20:25:35.582: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ** (umockdev-run:3858): DEBUG: 20:25:35.655: umockdev.vala:154: Removing test bed /tmp/umockdev.TQY612 127s (umockdev-run:3858): GLib-DEBUG: 20:25:35.661: unsetenv() is not thread-safe and should not be used after threads are created 127s Comparing PNGs /tmp/libfprint-umockdev-test-d4fexwu_/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 127s PASS: libfprint-2/driver-vfs5011.test 127s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.94.1.test 127s TAP version 14 127s # random seed: R02S689fcf65551f3658aca6dcaf5ac368f8 127s 1..14 127s # Start of device tests 127s # Start of async tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 1 /device/async/open 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 2 /device/async/close 127s # End of async tests 127s # Start of sync tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 3 /device/sync/open 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 4 /device/sync/close 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 5 /device/sync/get_driver 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 6 /device/sync/get_device_id 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 7 /device/sync/get_name 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 8 /device/sync/get_scan_type 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 9 /device/sync/get_nr_enroll_stages 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 10 /device/sync/supports_identify 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 11 /device/sync/supports_capture 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 12 /device/sync/has_storage 127s # Start of open tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 13 /device/sync/open/notify 127s # End of open tests 127s # Start of close tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fd09d3, GType is 101880234903424 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x762ba0fcab7b, GType is 101880234908096 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 14 /device/sync/close/notify 127s # End of close tests 127s # End of sync tests 127s # End of device tests 127s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.94.1.test 127s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.2.test 127s (process:3901): libfprint-context-DEBUG: 20:25:35.712: Initializing FpContext (libfprint version 1.94.8+tod1) 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.712: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.712: Found TOD entry point symbol 0x7c2b8ea88987, GType is 100475481867072 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.712: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.712: Initializing features for driver ssm_test_dev_tod_v1+1.90.2 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.712: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.713: Found TOD entry point symbol 0x7c2b8ea8253b, GType is 100475481876880 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.713: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 127s (process:3901): libfprint-tod-DEBUG: 20:25:35.713: Initializing features for driver fake_test_dev_tod_v1+1.90.2 127s (process:3901): libfprint-context-DEBUG: 20:25:35.713: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s (process:3901): libfprint-context-DEBUG: 20:25:35.714: created 127s (process:3901): libfprint-device-DEBUG: 20:25:35.714: Device reported probe completion 127s (process:3901): libfprint-device-DEBUG: 20:25:35.714: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s (process:3901): libfprint-device-DEBUG: 20:25:35.714: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:3901): GLib-DEBUG: 20:25:35.714: setenv()/putenv() are not thread-safe and should not be used after threads are created 127s TAP version 14 127s # random seed: R02S12490b32c0346ed5abdffd0c15f60b66 127s 1..97 127s # Start of driver tests 127s ok 1 /driver/get_driver 127s ok 2 /driver/get_device_id 127s ok 3 /driver/get_name 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 4 /driver/is_open 127s ok 5 /driver/get_nr_enroll_stages 127s ok 6 /driver/set_nr_enroll_stages 127s ok 7 /driver/supports_identify 127s ok 8 /driver/supports_capture 127s ok 9 /driver/has_storage 127s ok 10 /driver/do_not_support_identify 127s ok 11 /driver/do_not_support_capture 127s ok 12 /driver/has_not_storage 127s ok 13 /driver/get_usb_device 127s ok 14 /driver/get_virtual_env 127s ok 15 /driver/get_driver_data 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 16 /driver/initial_features 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 17 /driver/probe 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 18 /driver/open 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 19 /driver/close 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 20 /driver/enroll 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 21 /driver/verify 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 22 /driver/identify 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported capture completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 127s ok 23 /driver/capture 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported listing completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 24 /driver/list 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 25 /driver/delete 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 26 /driver/clear_storage # SKIP Feature not supported by TODv1 versions before 1.92.0 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 27 /driver/cancel 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 28 /driver/critical # SKIP Feature not supported by TODv1 versions before 1.94.0 127s ok 29 /driver/get_current_action 127s ok 30 /driver/timeout 127s ok 31 /driver/error_types 127s ok 32 /driver/retry_error_types 127s # Start of get_scan_type tests 127s ok 33 /driver/get_scan_type/press 127s ok 34 /driver/get_scan_type/swipe 127s # End of get_scan_type tests 127s # Start of set_scan_type tests 127s ok 35 /driver/set_scan_type/press 127s ok 36 /driver/set_scan_type/swipe 127s # End of set_scan_type tests 127s # Start of finger_status tests 127s ok 37 /driver/finger_status/inactive 127s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 127s ok 38 /driver/finger_status/waiting 127s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 127s ok 39 /driver/finger_status/present 127s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 127s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 127s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 127s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 127s ok 40 /driver/finger_status/changes 127s # End of finger_status tests 127s # Start of features tests 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 41 /driver/features/probe_updates # SKIP Feature not supported by TODv1 versions before 1.92.0 127s # End of features tests 127s # Start of initial_features tests 127s ok 42 /driver/initial_features/none 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 43 /driver/initial_features/no_capture 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 44 /driver/initial_features/no_verify 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 45 /driver/initial_features/no_identify 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 46 /driver/initial_features/no_storage 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 47 /driver/initial_features/no_list 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 48 /driver/initial_features/no_delete 127s ok 49 /driver/initial_features/no_clear 127s # End of initial_features tests 127s # Start of probe tests 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 50 /driver/probe/error 127s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 51 /driver/probe/action_error 127s # End of probe tests 127s # Start of open tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 52 /driver/open/error 127s # End of open tests 127s # Start of close tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 53 /driver/close/error 127s # End of close tests 127s # Start of enroll tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 54 /driver/enroll/error 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported enroll progress, reported 1817463179 of 1682569708 have been completed 127s # libfprint-device-DEBUG: Device reported enroll progress, reported 1848782212 of 1682569708 have been completed 127s # libfprint-device-DEBUG: Device reported enroll progress, reported 1740328816 of 1682569708 have been completed 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 55 /driver/enroll/progress 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 56 /driver/enroll/update_nbis 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 57 /driver/enroll/update_nbis_wrong_device 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 58 /driver/enroll/update_nbis_wrong_driver 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 59 /driver/enroll/update_nbis_missing_feature 127s # Start of error tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 60 /driver/enroll/error/no_print 127s # End of error tests 127s # End of enroll tests 127s # Start of verify tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 61 /driver/verify/fail 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 62 /driver/verify/retry 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 127s ok 63 /driver/verify/error 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 64 /driver/verify/not_supported 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 65 /driver/verify/report_no_cb 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 66 /driver/verify/not_reported 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 67 /driver/verify/complete_retry 127s # End of verify tests 127s # Start of identify tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 68 /driver/identify/fail 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 69 /driver/identify/retry 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 70 /driver/identify/error 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 71 /driver/identify/not_reported 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 72 /driver/identify/complete_retry 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 73 /driver/identify/report_no_cb 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 74 /driver/identify/suspend_continues # SKIP Feature not supported by TODv1 versions before 1.94.0 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 75 /driver/identify/suspend_succeeds # SKIP Feature not supported by TODv1 versions before 1.94.0 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 76 /driver/identify/suspend_busy_error # SKIP Feature not supported by TODv1 versions before 1.94.0 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 77 /driver/identify/suspend_while_idle # SKIP Feature not supported by TODv1 versions before 1.94.0 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 78 /driver/identify/warmup_cooldown # SKIP Feature not supported by TODv1 versions before 1.94.0 127s # End of identify tests 127s # Start of capture tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 79 /driver/capture/not_supported 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported capture completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 80 /driver/capture/error 127s # End of capture tests 127s # Start of list tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported listing completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 81 /driver/list/error 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 82 /driver/list/no_storage 127s # End of list tests 127s # Start of delete tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 83 /driver/delete/error 127s # End of delete tests 127s # Start of clear_storage tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 84 /driver/clear_storage/error # SKIP Feature not supported by TODv1 versions before 1.92.0 127s # End of clear_storage tests 127s # Start of cancel tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 85 /driver/cancel/fail 127s # End of cancel tests 127s # Start of get_current_action tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 86 /driver/get_current_action/open 127s # End of get_current_action tests 127s # Start of get_cancellable tests 127s ok 87 /driver/get_cancellable/error 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 88 /driver/get_cancellable/open 127s # Start of open tests 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 89 /driver/get_cancellable/open/internal 127s # End of open tests 127s # End of get_cancellable tests 127s # Start of action_is_cancelled tests 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 90 /driver/action_is_cancelled/open # SKIP Feature not supported by TODv1 versions before 1.94.0 127s ok 91 /driver/action_is_cancelled/error 127s # Start of open tests 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s ok 92 /driver/action_is_cancelled/open/internal # SKIP Feature not supported by TODv1 versions before 1.94.0 127s # End of open tests 127s # End of action_is_cancelled tests 127s # Start of complete_action tests 127s # Start of all tests 127s ok 93 /driver/complete_action/all/error 127s # End of all tests 127s # End of complete_action tests 127s # Start of action_error tests 127s ok 94 /driver/action_error/error 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 127s # libfprint-device-DEBUG: Device reported capture completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 127s # libfprint-device-DEBUG: Device reported listing completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 95 /driver/action_error/all 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported capture completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported listing completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.2' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.2' 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 96 /driver/action_error/fail 127s # End of action_error tests 127s # Start of timeout tests 127s ok 97 /driver/timeout/cancelled 127s # End of timeout tests 127s # End of driver tests 127s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.2.test 127s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.94.7.test 127s TAP version 14 127s # random seed: R02Sc119f353c079d21ac4429b5a448d528d 127s 1..14 127s # Start of device tests 127s # Start of async tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 1 /device/async/open 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 2 /device/async/close 127s # End of async tests 127s # Start of sync tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 3 /device/sync/open 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 4 /device/sync/close 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 5 /device/sync/get_driver 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 6 /device/sync/get_device_id 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 7 /device/sync/get_name 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 8 /device/sync/get_scan_type 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 9 /device/sync/get_nr_enroll_stages 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 10 /device/sync/supports_identify 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 11 /device/sync/supports_capture 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 12 /device/sync/has_storage 127s # Start of open tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 13 /device/sync/open/notify 127s # End of open tests 127s # Start of close tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac69d3, GType is 96243675654016 127s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x707f41ac0b7b, GType is 96243675658688 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 14 /device/sync/close/notify 127s # End of close tests 127s # End of sync tests 127s # End of device tests 127s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.94.7.test 127s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 127s TAP version 14 127s # random seed: R02Sb0aa8b873addaf87e7689ce9282645e9 127s 1..4 127s # Start of context tests 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7a08ff5d34b0, GType is 110895321763072 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 127s ok 1 /context/new 127s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 127s ok 2 /context/no-devices 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7a08ff5d34b0, GType is 110895321763072 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 3 /context/has-virtual-device 127s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 127s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 127s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7a08ff5d34b0, GType is 110895321763072 127s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 127s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s # libfprint-context-DEBUG: created 127s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 4 /context/enumerates-new-devices 127s # End of context tests 127s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 127s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.3.test 127s (process:3951): libfprint-context-DEBUG: 20:25:35.959: Initializing FpContext (libfprint version 1.94.8+tod1) 127s (process:3951): libfprint-tod-DEBUG: 20:25:35.959: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 127s (process:3951): libfprint-tod-DEBUG: 20:25:35.960: Found TOD entry point symbol 0x7d03cba369d3, GType is 97954696557376 127s (process:3951): libfprint-tod-DEBUG: 20:25:35.960: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 127s (process:3951): libfprint-tod-DEBUG: 20:25:35.960: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 127s (process:3951): libfprint-tod-DEBUG: 20:25:35.960: Found TOD entry point symbol 0x7d03cba30b7b, GType is 97954696567392 127s (process:3951): libfprint-tod-DEBUG: 20:25:35.960: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 127s (process:3951): libfprint-context-DEBUG: 20:25:35.961: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 127s (process:3951): libfprint-context-DEBUG: 20:25:35.961: created 127s (process:3951): libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: 20:25:35.961: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s 127s (process:3951): libfprint-device-DEBUG: 20:25:35.961: Device reported probe completion 127s (process:3951): libfprint-device-DEBUG: 20:25:35.961: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s (process:3951): libfprint-device-DEBUG: 20:25:35.961: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:3951): GLib-DEBUG: 20:25:35.961: setenv()/putenv() are not thread-safe and should not be used after threads are created 127s TAP version 14 127s # random seed: R02Sdae43b199d7d7dea3ef2547ff79d725b 127s 1..97 127s # Start of driver tests 127s ok 1 /driver/get_driver 127s ok 2 /driver/get_device_id 127s ok 3 /driver/get_name 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 4 /driver/is_open 127s ok 5 /driver/get_nr_enroll_stages 127s ok 6 /driver/set_nr_enroll_stages 127s ok 7 /driver/supports_identify 127s ok 8 /driver/supports_capture 127s ok 9 /driver/has_storage 127s ok 10 /driver/do_not_support_identify 127s ok 11 /driver/do_not_support_capture 127s ok 12 /driver/has_not_storage 127s ok 13 /driver/get_usb_device 127s ok 14 /driver/get_virtual_env 127s ok 15 /driver/get_driver_data 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 127s ok 16 /driver/initial_features 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 127s # 127s # libfprint-device-DEBUG: Device reported probe completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 17 /driver/probe 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 18 /driver/open 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 19 /driver/close 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 127s # 127s # libfprint-device-DEBUG: Device reported enroll completion 127s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 20 /driver/enroll 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 127s # 127s # libfprint-device-DEBUG: Device reported verify result 127s # libfprint-device-DEBUG: Device reported verify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 21 /driver/verify 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 127s # 127s # libfprint-device-DEBUG: Device reported identify result 127s # libfprint-device-DEBUG: Device reported identify completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 22 /driver/identify 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 127s # 127s # libfprint-device-DEBUG: Device reported capture completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 127s ok 23 /driver/capture 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 127s # 127s # libfprint-device-DEBUG: Device reported listing completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 24 /driver/list 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 127s # 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 25 /driver/delete 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 127s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 127s # 127s # libfprint-device-DEBUG: Device reported deletion completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 127s # 127s # libfprint-device-DEBUG: Device reported close completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s ok 26 /driver/clear_storage 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 127s # 127s # libfprint-device-DEBUG: Device reported open completion 127s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 127s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 127s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 127s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 127s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 128s # 128s # libfprint-device-DEBUG: Device reported deletion completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 27 /driver/cancel 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 128s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 128s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 128s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 128s # 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 28 /driver/critical 128s ok 29 /driver/get_current_action 128s ok 30 /driver/timeout 128s ok 31 /driver/error_types 128s ok 32 /driver/retry_error_types 128s # Start of get_scan_type tests 128s ok 33 /driver/get_scan_type/press 128s ok 34 /driver/get_scan_type/swipe 128s # End of get_scan_type tests 128s # Start of set_scan_type tests 128s ok 35 /driver/set_scan_type/press 128s ok 36 /driver/set_scan_type/swipe 128s # End of set_scan_type tests 128s # Start of finger_status tests 128s ok 37 /driver/finger_status/inactive 128s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 128s ok 38 /driver/finger_status/waiting 128s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 128s ok 39 /driver/finger_status/present 128s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 128s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 128s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 128s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 128s ok 40 /driver/finger_status/changes 128s # End of finger_status tests 128s # Start of features tests 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 128s # 128s # libfprint-device-DEBUG: Device reported probe completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 41 /driver/features/probe_updates 128s # End of features tests 128s # Start of initial_features tests 128s ok 42 /driver/initial_features/none 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s ok 43 /driver/initial_features/no_capture 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s ok 44 /driver/initial_features/no_verify 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s ok 45 /driver/initial_features/no_identify 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s ok 46 /driver/initial_features/no_storage 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s ok 47 /driver/initial_features/no_list 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s ok 48 /driver/initial_features/no_delete 128s ok 49 /driver/initial_features/no_clear 128s # End of initial_features tests 128s # Start of probe tests 128s # libfprint-device-DEBUG: Device reported probe completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 50 /driver/probe/error 128s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 128s # libfprint-device-DEBUG: Device reported probe completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 51 /driver/probe/action_error 128s # End of probe tests 128s # Start of open tests 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 52 /driver/open/error 128s # End of open tests 128s # Start of close tests 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 53 /driver/close/error 128s # End of close tests 128s # Start of enroll tests 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 128s # 128s # libfprint-device-DEBUG: Device reported enroll completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 54 /driver/enroll/error 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported enroll progress, reported 1842727079 of 1625200517 have been completed 128s # libfprint-device-DEBUG: Device reported enroll progress, reported 1963349201 of 1625200517 have been completed 128s # libfprint-device-DEBUG: Device reported enroll progress, reported 2048601998 of 1625200517 have been completed 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 128s # 128s # libfprint-device-DEBUG: Device reported enroll completion 128s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 55 /driver/enroll/progress 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 128s # 128s # libfprint-device-DEBUG: Device reported enroll completion 128s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 56 /driver/enroll/update_nbis 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 57 /driver/enroll/update_nbis_wrong_device 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 58 /driver/enroll/update_nbis_wrong_driver 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 59 /driver/enroll/update_nbis_missing_feature 128s # Start of error tests 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported enroll completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Device reported enroll completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Device reported enroll completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 60 /driver/enroll/error/no_print 128s # End of error tests 128s # End of enroll tests 128s # Start of verify tests 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 128s # 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 61 /driver/verify/fail 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 128s # 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 62 /driver/verify/retry 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 128s # 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 63 /driver/verify/error 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 64 /driver/verify/not_supported 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 65 /driver/verify/report_no_cb 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 66 /driver/verify/not_reported 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Device reported verify result 128s # libfprint-device-DEBUG: Device reported verify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 67 /driver/verify/complete_retry 128s # End of verify tests 128s # Start of identify tests 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 128s ok 68 /driver/identify/fail 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 69 /driver/identify/retry 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 70 /driver/identify/error 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 71 /driver/identify/not_reported 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 72 /driver/identify/complete_retry 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 73 /driver/identify/report_no_cb 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 74 /driver/identify/suspend_continues 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-device-DEBUG: Device reported identify result 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 75 /driver/identify/suspend_succeeds 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 128s # 128s # libfprint-device-DEBUG: Device reported identify completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 128s ok 76 /driver/identify/suspend_busy_error 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 128s # 128s # libfprint-device-DEBUG: Device reported close completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s ok 77 /driver/identify/suspend_while_idle 128s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 128s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 128s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 128s # 128s # libfprint-device-DEBUG: Device reported open completion 128s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 128s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 129s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.3.test 130s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 130s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 130s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 130s # 130s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 130s # 130s # libfprint-device-DEBUG: Device reported identify completion 130s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 130s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 130s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 130s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 132s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 134s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.3.test 135s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 78 /driver/identify/warmup_cooldown 135s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 135s # End of identify tests 135s # Start of capture tests 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 79 /driver/capture/not_supported 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 135s # 135s # libfprint-device-DEBUG: Device reported capture completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 80 /driver/capture/error 135s # End of capture tests 135s # Start of list tests 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 135s # 135s # libfprint-device-DEBUG: Device reported listing completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 81 /driver/list/error 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 82 /driver/list/no_storage 135s # End of list tests 135s # Start of delete tests 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 83 /driver/delete/error 135s # End of delete tests 135s # Start of clear_storage tests 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 84 /driver/clear_storage/error 135s # End of clear_storage tests 135s # Start of cancel tests 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 85 /driver/cancel/fail 135s # End of cancel tests 135s # Start of get_current_action tests 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 86 /driver/get_current_action/open 135s # End of get_current_action tests 135s # Start of get_cancellable tests 135s ok 87 /driver/get_cancellable/error 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 88 /driver/get_cancellable/open 135s # Start of open tests 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 89 /driver/get_cancellable/open/internal 135s # End of open tests 135s # End of get_cancellable tests 135s # Start of action_is_cancelled tests 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 90 /driver/action_is_cancelled/open 135s ok 91 /driver/action_is_cancelled/error 135s # Start of open tests 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 92 /driver/action_is_cancelled/open/internal 135s # End of open tests 135s # End of action_is_cancelled tests 135s # Start of complete_action tests 135s # Start of all tests 135s ok 93 /driver/complete_action/all/error 135s # End of all tests 135s # End of complete_action tests 135s # Start of action_error tests 135s ok 94 /driver/action_error/error 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 135s # libfprint-device-DEBUG: Device reported enroll completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 135s # libfprint-device-DEBUG: Device reported verify completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 135s # libfprint-device-DEBUG: Device reported identify completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 135s # libfprint-device-DEBUG: Device reported capture completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 135s # libfprint-device-DEBUG: Device reported listing completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 95 /driver/action_error/all 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 135s # 135s # libfprint-device-DEBUG: Device reported enroll completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 135s # 135s # libfprint-device-DEBUG: Device reported verify completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 135s # 135s # libfprint-device-DEBUG: Device reported identify completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 135s # 135s # libfprint-device-DEBUG: Device reported capture completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 135s # 135s # libfprint-device-DEBUG: Device reported listing completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.3' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.3' 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 96 /driver/action_error/fail 135s # End of action_error tests 135s # Start of timeout tests 135s ok 97 /driver/timeout/cancelled 135s # End of timeout tests 135s # End of driver tests 135s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.3.test 135s Running test: libfprint-2/driver-egismoc-0586.test 135s ** (umockdev-run:3959): DEBUG: 20:25:43.506: umockdev.vala:127: Created udev test bed /tmp/umockdev.ADV912 135s ** (umockdev-run:3959): DEBUG: 20:25:43.506: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 135s ** (umockdev-run:3959): DEBUG: 20:25:43.507: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 135s ** (umockdev-run:3959): DEBUG: 20:25:43.511: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.ADV912/dev/bus/usb/001/021 135s ** (umockdev-run:3959): DEBUG: 20:25:43.511: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 135s ** (umockdev-run:3959): DEBUG: 20:25:43.512: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 135s ** (umockdev-run:3959): DEBUG: 20:25:43.515: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.ADV912/dev/bus/usb/001/001 135s ** (umockdev-run:3959): DEBUG: 20:25:43.515: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 135s ** (umockdev-run:3959): DEBUG: 20:25:43.515: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 135s (process:3963): libfprint-context-DEBUG: 20:25:43.592: Initializing FpContext (libfprint version 1.94.8+tod1) 135s (process:3963): libfprint-tod-DEBUG: 20:25:43.593: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.595: 103390667: ../libfprint/drivers/egismoc/egismoc.c:1597 135s (process:3963): libfprint-context-DEBUG: 20:25:43.595: No driver found for USB device 1D6B:0002 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.595: egismoc_probe enter --> 135s (process:3963): libfprint-device-DEBUG: 20:25:43.596: Device reported probe completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.597: Completing action FPI_DEVICE_ACTION_PROBE in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.597: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.598: Opening device 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.598: [egismoc] DEV_INIT_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.599: [egismoc] DEV_INIT_STATES entering state 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.599: [egismoc] DEV_INIT_STATES entering state 2 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.600: [egismoc] DEV_INIT_STATES entering state 3 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.601: [egismoc] DEV_INIT_STATES entering state 4 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.601: [egismoc] DEV_INIT_STATES entering state 5 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.601: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.601: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.601: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.602: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.602: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.602: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.602: Firmware version callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.602: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.602: Device firmware version is 9050.6.2.56 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.602: [egismoc] DEV_INIT_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.602: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.602: Device reported open completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.602: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.602: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.603: List 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.603: [egismoc] LIST_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.603: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.603: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.603: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.603: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.604: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.604: [egismoc] LIST_STATES entering state 1 135s (process:3963): libfprint-device-DEBUG: 20:25:43.604: Device reported listing completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.604: [egismoc] LIST_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.604: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.604: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: Clear storage 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.604: [egismoc] DELETE_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.604: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.604: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.605: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.605: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.606: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.606: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.606: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.606: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.606: [egismoc] DELETE_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.606: Get delete command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.606: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.606: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.606: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.606: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.607: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.607: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.607: Delete callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.607: Response prefix valid: yes 135s (process:3963): libfprint-device-DEBUG: 20:25:43.607: Device reported deletion completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.607: [egismoc] DELETE_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.607: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.607: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.607: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.607: List 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.607: [egismoc] LIST_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.607: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.607: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.607: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.608: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.608: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.608: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.608: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.608: Number of currently enrolled fingerprints on the device is 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.608: [egismoc] LIST_STATES entering state 1 135s (process:3963): libfprint-device-DEBUG: 20:25:43.608: Device reported listing completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.608: [egismoc] LIST_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.608: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.608: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.608: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:3963): libfprint-device-DEBUG: 20:25:43.609: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.609: Enroll 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.609: [egismoc] ENROLL_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.609: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.609: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.609: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.609: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.610: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.610: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.610: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.610: Number of currently enrolled fingerprints on the device is 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.610: [egismoc] ENROLL_STATES entering state 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.610: [egismoc] ENROLL_STATES entering state 2 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.610: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.610: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.610: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.611: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.611: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.611: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.611: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.611: [egismoc] ENROLL_STATES entering state 3 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.611: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.611: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.611: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.612: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.612: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.612: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.612: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.612: [egismoc] ENROLL_STATES entering state 4 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.612: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.612: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.613: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.613: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.613: [egismoc] ENROLL_STATES entering state 5 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.613: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.613: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.613: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.613: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.614: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.614: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.614: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.614: [egismoc] ENROLL_STATES entering state 6 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.614: Get check command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.614: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.614: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.614: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.614: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.615: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.615: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.615: Enroll check callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.615: Response suffix valid: yes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.615: [egismoc] ENROLL_STATES entering state 7 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.615: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.615: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.615: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.615: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.616: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.616: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.616: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.616: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.616: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.616: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.616: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.616: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.617: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.617: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.617: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.617: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.617: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.617: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.617: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.617: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.618: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.618: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.618: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.618: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.618: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.618: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.618: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.618: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.618: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.618: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.618: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.619: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.619: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.619: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.619: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.619: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.619: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.619: Partial capture successful. Please touch the sensor again (1/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.619: Device reported enroll progress, reported 1 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.619: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.619: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.619: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.619: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.620: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.620: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.620: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.620: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.620: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.620: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.620: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.620: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.621: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.621: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.621: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.621: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.621: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.621: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.622: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.622: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.622: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.622: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.622: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.622: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.622: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.623: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.623: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.623: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.623: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.623: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.623: Partial capture successful. Please touch the sensor again (2/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.623: Device reported enroll progress, reported 2 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.623: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.623: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.623: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.623: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.623: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.624: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.624: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.624: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.624: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.624: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.624: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.624: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.625: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.625: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.625: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.625: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.625: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.625: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.626: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.626: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.626: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.626: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.626: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.626: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.626: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.627: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.627: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.627: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.627: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.627: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.627: Partial capture successful. Please touch the sensor again (3/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.627: Device reported enroll progress, reported 3 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.627: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.627: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.627: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.627: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.628: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.628: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.628: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.628: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.628: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.628: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.628: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.628: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.629: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.629: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.629: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.629: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.629: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.629: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.630: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.630: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.630: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.630: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.630: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.630: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.630: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.631: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.631: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.631: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.631: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.631: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.631: Partial capture successful. Please touch the sensor again (4/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.631: Device reported enroll progress, reported 4 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.631: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.631: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.631: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.631: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.631: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.632: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.632: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.632: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.632: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.632: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.632: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.632: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.632: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.632: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.633: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.633: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.633: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.633: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.633: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.633: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.633: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.633: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.633: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.633: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.633: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.634: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.634: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.634: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.634: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.634: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.634: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.634: Partial capture successful. Please touch the sensor again (5/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.634: Device reported enroll progress, reported 5 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.634: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.634: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.634: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.634: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.634: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.635: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.635: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.635: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.635: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.635: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.635: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.635: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.635: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.636: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.636: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.636: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.636: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.636: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.636: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.636: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.636: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.636: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.636: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.636: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.636: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.637: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.637: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.637: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.637: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.637: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.637: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.637: Partial capture successful. Please touch the sensor again (6/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.637: Device reported enroll progress, reported 6 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.637: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.637: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.637: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.637: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.638: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.638: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.638: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.638: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.638: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.638: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.638: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.638: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.639: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.639: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.639: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.639: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.639: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.639: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.639: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.640: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.640: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.640: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.640: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.640: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.640: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.640: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.641: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.641: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.641: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.641: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.641: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.641: Partial capture successful. Please touch the sensor again (7/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.641: Device reported enroll progress, reported 7 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.641: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.641: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.641: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.641: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.641: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.642: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.642: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.642: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.642: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.642: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.642: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.642: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.642: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.643: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.643: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.643: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.643: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.643: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.643: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.643: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.644: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.644: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.644: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.644: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.644: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Response suffix valid: NO 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.644: Response suffix valid: yes 135s (process:3963): libfprint-device-DEBUG: 20:25:43.644: Device reported enroll progress, reported 7 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.645: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.645: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.645: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.645: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.645: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.645: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.645: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.645: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.645: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.645: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.645: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.645: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.646: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.646: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.646: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.646: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.646: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.646: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.646: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.647: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.647: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.647: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.647: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.647: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.647: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.647: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.648: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.648: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.648: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.648: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.648: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.648: Partial capture successful. Please touch the sensor again (8/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.648: Device reported enroll progress, reported 8 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.648: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.648: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.648: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.648: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.648: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.649: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.649: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.649: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.649: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.649: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.649: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.649: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.649: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.650: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.650: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.650: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.650: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.650: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.650: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.650: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.650: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.650: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.650: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.650: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.650: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.651: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.651: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Response suffix valid: NO 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Response suffix valid: yes 135s (process:3963): libfprint-device-DEBUG: 20:25:43.651: Device reported enroll progress, reported 8 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.651: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.651: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.651: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.652: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.652: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.652: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.652: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.652: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.652: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.652: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.652: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.653: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.653: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.653: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.653: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.653: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.653: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.653: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.654: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.654: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.654: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.654: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.654: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.654: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.654: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.655: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.655: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.655: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.655: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.655: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.655: Partial capture successful. Please touch the sensor again (9/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.655: Device reported enroll progress, reported 9 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.655: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.655: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.655: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.655: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.655: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.656: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.656: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.656: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.656: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.656: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.656: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.656: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.656: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.657: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.657: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.657: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.657: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.657: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.657: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.657: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.657: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.657: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.657: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.657: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.658: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.658: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.658: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.658: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.658: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.658: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.658: Partial capture successful. Please touch the sensor again (10/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.658: Device reported enroll progress, reported 10 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.658: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.658: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.658: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.658: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.659: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.659: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.659: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.659: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.659: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.659: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.659: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.659: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.660: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.660: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.660: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.660: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.660: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.660: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.660: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.661: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.661: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.661: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.661: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.661: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.661: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.661: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.662: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.662: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.662: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.662: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.662: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.662: Partial capture successful. Please touch the sensor again (11/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.662: Device reported enroll progress, reported 11 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.662: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.662: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.662: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.662: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.662: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.663: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.663: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.663: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.663: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.663: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.663: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.663: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.664: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.664: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.664: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.664: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.664: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.664: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.665: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.665: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.665: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.665: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.665: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.665: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.665: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.666: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.666: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.666: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.666: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.666: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.666: Partial capture successful. Please touch the sensor again (12/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.666: Device reported enroll progress, reported 12 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.666: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.666: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.666: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.666: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.667: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.667: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.667: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.667: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.667: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.667: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.667: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.667: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.668: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.668: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.668: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.668: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.668: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.668: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.668: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.669: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.669: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.669: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.669: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.669: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.669: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.670: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.670: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.670: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.670: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.670: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.670: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.670: Partial capture successful. Please touch the sensor again (13/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.670: Device reported enroll progress, reported 13 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.670: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.670: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.670: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.670: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.671: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.671: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.671: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.671: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.671: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.671: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.671: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.671: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.672: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.673: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.673: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.673: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.673: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.673: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.673: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.674: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.674: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.674: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.674: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.674: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.674: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.674: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.675: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.675: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.675: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.675: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.675: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.675: Partial capture successful. Please touch the sensor again (14/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.675: Device reported enroll progress, reported 14 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.675: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.675: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.675: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.675: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.675: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.676: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.676: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.676: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.676: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.676: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.676: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.676: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.676: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.676: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.676: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.676: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.676: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.676: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.676: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.677: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.677: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.677: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.677: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.677: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.677: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.677: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.678: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Partial capture successful. Please touch the sensor again (15/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.678: Device reported enroll progress, reported 15 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.678: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.678: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.678: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.678: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.679: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.679: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.679: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.679: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.679: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.679: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.679: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.679: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.679: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.679: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.679: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.679: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.679: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.680: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.680: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.680: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.680: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.680: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.680: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.680: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.681: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.681: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.681: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.681: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.681: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.681: Partial capture successful. Please touch the sensor again (16/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.681: Device reported enroll progress, reported 16 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.681: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.681: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.681: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.681: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.681: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.682: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.682: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.682: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.682: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.682: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.682: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.682: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.682: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.682: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.682: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.682: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.682: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.682: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.682: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.683: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.683: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.683: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.683: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.683: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.683: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.683: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.684: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.684: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.684: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.684: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.684: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.684: Partial capture successful. Please touch the sensor again (17/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.684: Device reported enroll progress, reported 17 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.684: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.684: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.684: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.684: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.684: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.685: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.685: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.685: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.685: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.685: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.685: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.685: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.685: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.686: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.686: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.686: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.686: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.686: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.686: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.686: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.686: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.686: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.686: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.686: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.686: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.686: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.687: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.687: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.687: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.687: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.687: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.687: Partial capture successful. Please touch the sensor again (18/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.687: Device reported enroll progress, reported 18 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.687: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.687: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.687: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.687: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.687: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.688: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.688: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.688: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.688: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.688: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.688: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.688: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.688: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.688: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.688: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.688: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.688: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.688: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.689: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.689: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.689: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.689: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.689: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.689: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.689: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.690: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Partial capture successful. Please touch the sensor again (19/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.690: Device reported enroll progress, reported 19 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.690: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.690: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.690: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.690: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.690: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.690: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.690: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.691: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.691: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.691: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.691: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.691: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.691: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.692: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.692: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.692: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.692: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.692: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Partial capture successful. Please touch the sensor again (20/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.692: Device reported enroll progress, reported 20 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.692: [egismoc] ENROLL_STATES entering state 12 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.692: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.692: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.693: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.693: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.693: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.693: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.693: [egismoc] ENROLL_STATES entering state 13 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.693: New fingerprint ID: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.693: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.693: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.693: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.694: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.694: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.694: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.694: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.694: [egismoc] ENROLL_STATES entering state 14 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.694: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.694: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.694: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.694: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.695: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.695: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.695: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.695: [egismoc] ENROLL_STATES entering state 15 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.695: Enrollment was successful! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.695: Device reported enroll completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.695: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:3963): libfprint-device-DEBUG: 20:25:43.695: Print for finger FP_FINGER_LEFT_INDEX enrolled 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.695: [egismoc] ENROLL_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.695: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.695: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.695: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.695: List 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.695: [egismoc] LIST_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.695: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.695: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.695: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.695: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.696: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.696: [egismoc] LIST_STATES entering state 1 135s (process:3963): libfprint-device-DEBUG: 20:25:43.696: Device reported listing completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.696: [egismoc] LIST_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.696: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.696: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-device-DEBUG: 20:25:43.696: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: Identify or Verify 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.696: [egismoc] IDENTIFY_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.696: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.696: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.697: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.697: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.697: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.697: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.697: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.697: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.697: [egismoc] IDENTIFY_STATES entering state 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.697: [egismoc] IDENTIFY_STATES entering state 2 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.697: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.697: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.697: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.698: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.698: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.698: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.698: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.698: [egismoc] IDENTIFY_STATES entering state 3 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.698: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.698: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.698: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.698: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.699: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.699: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.699: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.699: [egismoc] IDENTIFY_STATES entering state 4 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.699: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.699: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.699: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.699: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.699: [egismoc] IDENTIFY_STATES entering state 5 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.699: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.699: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.699: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.700: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.700: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.700: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.700: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.700: [egismoc] IDENTIFY_STATES entering state 6 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.700: Get check command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.700: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.700: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.700: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.700: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.701: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.701: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.701: Identify check callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.701: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.701: Identify successful for: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.701: Verifying against: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-device-DEBUG: 20:25:43.701: Device reported verify result 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.701: [egismoc] IDENTIFY_STATES entering state 7 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.701: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.701: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.701: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.701: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.702: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.702: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.702: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.702: [egismoc] IDENTIFY_STATES entering state 8 135s (process:3963): libfprint-device-DEBUG: 20:25:43.702: Device reported verify completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.702: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.702: [egismoc] IDENTIFY_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.702: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.702: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.702: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-device-DEBUG: 20:25:43.702: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.702: Identify or Verify 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.702: [egismoc] IDENTIFY_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.702: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.702: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.702: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.703: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.703: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.703: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.703: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.703: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.703: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.703: [egismoc] IDENTIFY_STATES entering state 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.703: [egismoc] IDENTIFY_STATES entering state 2 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.703: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.703: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.703: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.704: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.704: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.704: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.704: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.704: [egismoc] IDENTIFY_STATES entering state 3 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.704: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.704: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.704: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.705: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.705: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.705: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.705: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.705: [egismoc] IDENTIFY_STATES entering state 4 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.705: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.705: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.705: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.705: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.705: [egismoc] IDENTIFY_STATES entering state 5 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.705: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.706: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.706: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.706: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.706: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.706: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.706: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.706: [egismoc] IDENTIFY_STATES entering state 6 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.706: Get check command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.706: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.706: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.706: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.707: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.707: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.707: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.707: Identify check callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.707: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.707: Identify successful for: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-device-DEBUG: 20:25:43.707: Device reported identify result 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.707: [egismoc] IDENTIFY_STATES entering state 7 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.707: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.707: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.707: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.708: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.708: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.708: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.708: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.708: [egismoc] IDENTIFY_STATES entering state 8 135s (process:3963): libfprint-device-DEBUG: 20:25:43.708: Device reported identify completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.708: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.708: [egismoc] IDENTIFY_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.708: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.708: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.708: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-device-DEBUG: 20:25:43.708: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.708: Enroll 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.708: [egismoc] ENROLL_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.708: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.708: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.708: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.709: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.709: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.709: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.709: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.709: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.709: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.709: [egismoc] ENROLL_STATES entering state 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.709: [egismoc] ENROLL_STATES entering state 2 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.709: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.709: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.709: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.710: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.710: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.710: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.710: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.710: [egismoc] ENROLL_STATES entering state 3 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.711: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.711: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.711: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.711: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.711: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.711: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.711: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.711: [egismoc] ENROLL_STATES entering state 4 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.711: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.711: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.712: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.712: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.712: [egismoc] ENROLL_STATES entering state 5 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.712: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.712: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.712: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.712: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.713: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.713: [egismoc] ENROLL_STATES entering state 6 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Get check command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.713: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.713: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.713: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Enroll check callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Response suffix valid: NO 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.713: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.713: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.713: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.713: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 135s (process:3963): libfprint-device-DEBUG: 20:25:43.713: Device reported enroll completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.713: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:3963): libfprint-device-DEBUG: 20:25:43.714: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.714: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.714: List 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.714: [egismoc] LIST_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.714: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.714: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.714: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.714: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.714: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.715: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.715: [egismoc] LIST_STATES entering state 1 135s (process:3963): libfprint-device-DEBUG: 20:25:43.715: Device reported listing completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.715: [egismoc] LIST_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.715: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.715: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-device-DEBUG: 20:25:43.715: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: Enroll 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.715: [egismoc] ENROLL_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.715: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.715: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.715: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.715: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.716: [egismoc] ENROLL_STATES entering state 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.716: [egismoc] ENROLL_STATES entering state 2 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.716: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.716: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.716: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.716: [egismoc] ENROLL_STATES entering state 3 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.716: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.716: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.717: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.717: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.717: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.717: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.717: [egismoc] ENROLL_STATES entering state 4 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.717: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.717: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.718: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.718: [egismoc] ENROLL_STATES entering state 5 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.718: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.718: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.718: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.718: [egismoc] ENROLL_STATES entering state 6 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Get check command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.718: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.718: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.719: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.719: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.719: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.719: Enroll check callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.719: Response suffix valid: yes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.719: [egismoc] ENROLL_STATES entering state 7 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.719: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.719: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.719: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.720: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.720: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.720: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.720: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.720: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.720: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.720: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.720: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.720: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.721: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.721: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.721: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.721: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.721: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.721: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.721: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.721: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.722: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.722: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.722: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.722: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.722: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.722: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.722: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.722: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.722: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.722: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.722: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.722: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.723: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.723: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.723: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.723: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.723: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.723: Partial capture successful. Please touch the sensor again (1/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.723: Device reported enroll progress, reported 1 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.723: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.723: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.723: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.723: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.723: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.724: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.724: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.724: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.724: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.724: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.724: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.724: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.724: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.724: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.724: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.724: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.724: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.724: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.725: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.725: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.725: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.725: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.725: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.725: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.725: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.726: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Partial capture successful. Please touch the sensor again (2/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.726: Device reported enroll progress, reported 2 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.726: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.726: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.726: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.726: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.726: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.726: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.726: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.727: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.727: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.727: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.727: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.727: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.727: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.728: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.728: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.728: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.728: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.728: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Partial capture successful. Please touch the sensor again (3/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.728: Device reported enroll progress, reported 3 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.728: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.728: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.729: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.729: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.729: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.729: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.729: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.729: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.729: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.729: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.729: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.729: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.730: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.730: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.730: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.730: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.730: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.730: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.730: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.730: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.731: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.731: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.731: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.731: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Partial capture successful. Please touch the sensor again (4/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.731: Device reported enroll progress, reported 4 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.731: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.731: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.731: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.732: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.732: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.732: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.732: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.732: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.732: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.732: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.732: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.732: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.733: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.733: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.733: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.733: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.733: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.733: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.733: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.733: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.733: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.733: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.733: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.733: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.734: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.734: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.734: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.734: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.734: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.734: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.734: Partial capture successful. Please touch the sensor again (5/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.734: Device reported enroll progress, reported 5 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.734: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.734: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.734: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.734: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.735: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.735: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.735: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.735: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.735: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.735: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.735: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.735: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.735: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.736: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.736: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.736: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.736: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.736: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.736: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.736: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.736: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.736: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.736: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.736: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.736: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.737: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.737: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.737: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.737: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.737: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.737: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.737: Partial capture successful. Please touch the sensor again (6/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.737: Device reported enroll progress, reported 6 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.737: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.737: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.737: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.737: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.737: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.738: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.738: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.738: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.738: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.738: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.738: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.738: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.738: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.739: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.739: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.739: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.739: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.739: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.739: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.739: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.739: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.739: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.739: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.739: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.739: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.739: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.740: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.740: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.740: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.740: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.740: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.740: Partial capture successful. Please touch the sensor again (7/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.740: Device reported enroll progress, reported 7 of 20 have been completed 135s listing - device should have prints 135s clear device storage 135s clear done 135s listing - device should be empty 135s enrolling 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 1, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 2, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 3, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 4, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 5, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 6, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 7, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 8, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 9, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 10, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 11, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 12, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 13, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 14, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 15, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 16, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 17, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 18, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 19, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 20, , None, None) 135s enroll done 135s listing - device should have 1 print 135s verifying 135s verify done 135s async identifying 135s indentification_done: 135s try to enroll duplicate 135s duplicate enroll attempt done 135s listing - device should still only have 1 print 135s enroll new finger 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 1, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 2, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 3, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 4, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 5, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 6, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 7, , None, None)(process:3963): libfprint-SSM-DEBUG: 20:25:43.740: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.740: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.740: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.740: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.740: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.741: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.741: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.741: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.741: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.741: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.741: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.741: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.741: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.742: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.742: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.742: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.742: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.742: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.742: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.742: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.742: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.742: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.742: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.742: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.742: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.742: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.743: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Response suffix valid: NO 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Response suffix valid: yes 135s (process:3963): libfprint-device-DEBUG: 20:25:43.743: Device reported enroll progress, reported 7 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.743: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.743: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.743: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.743: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.744: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.744: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.744: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.744: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.744: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.744: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.744: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.744: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.745: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.745: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.745: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.745: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.745: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.745: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.745: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.745: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.745: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.745: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.745: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.745: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.746: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.746: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.746: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.746: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.746: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.746: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.746: Partial capture successful. Please touch the sensor again (8/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.746: Device reported enroll progress, reported 8 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.746: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.746: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.746: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.746: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.746: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.747: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.747: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.747: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.747: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.747: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.747: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.747: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.747: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.748: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.748: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.748: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.748: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.748: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.748: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.748: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.748: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.748: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.748: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.748: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.748: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.749: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.749: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.749: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.749: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.749: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.749: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.749: Partial capture successful. Please touch the sensor again (9/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.749: Device reported enroll progress, reported 9 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.749: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.749: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.749: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.749: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.750: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.750: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.750: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.750: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.750: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.750: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.750: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.750: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.750: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.751: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.751: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.751: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.751: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.751: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.751: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.751: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.751: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.751: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.751: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.751: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.752: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.752: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Response suffix valid: NO 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Response suffix valid: yes 135s (process:3963): libfprint-device-DEBUG: 20:25:43.752: Device reported enroll progress, reported 9 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.752: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.752: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.752: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.752: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.753: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.753: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.753: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.753: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.753: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.753: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.753: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.753: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.754: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.754: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.754: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.754: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.754: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.754: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.754: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.754: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.754: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.754: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.754: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.754: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.755: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.755: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.755: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.755: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.755: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.755: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.755: Partial capture successful. Please touch the sensor again (10/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.755: Device reported enroll progress, reported 10 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.755: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.755: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.755: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.755: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.756: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.756: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.756: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.756: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.756: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.756: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.756: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.756: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.756: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.757: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.757: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.757: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.757: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.757: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.757: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.757: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.757: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.757: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.757: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.757: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.757: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.758: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.758: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.758: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.758: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.758: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.758: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.758: Partial capture successful. Please touch the sensor again (11/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.758: Device reported enroll progress, reported 11 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.758: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.758: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.758: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.758: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.759: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.759: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.759: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.759: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.759: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.759: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.759: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.759: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.759: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.760: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.760: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.760: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.760: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.760: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.760: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.760: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.760: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.760: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.760: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.760: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.761: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.761: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.761: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.761: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.761: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.761: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.761: Partial capture successful. Please touch the sensor again (12/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.761: Device reported enroll progress, reported 12 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.761: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.761: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.761: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.761: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.761: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.762: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.762: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.762: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.762: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.762: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.762: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.762: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.762: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.763: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.763: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.763: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.763: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.763: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.763: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.763: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.763: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.763: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.763: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.763: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.763: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.764: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.764: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.764: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.764: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.764: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.764: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.764: Partial capture successful. Please touch the sensor again (13/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.764: Device reported enroll progress, reported 13 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.764: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.764: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.764: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.764: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.764: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.765: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.765: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.765: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.765: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.765: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.765: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.765: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.765: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.766: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.766: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.766: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.766: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.766: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.766: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.766: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.766: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.766: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.766: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.766: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.767: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.767: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.767: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.767: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.767: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.767: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.767: Partial capture successful. Please touch the sensor again (14/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.767: Device reported enroll progress, reported 14 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.767: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.767: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.767: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.767: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.767: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.768: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.768: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.768: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.768: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.768: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.768: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.768: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.768: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.769: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.769: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.769: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.769: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.769: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.769: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.769: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.769: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.769: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.769: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.769: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.769: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.770: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.770: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.770: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.770: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.770: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.770: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.770: Partial capture successful. Please touch the sensor again (15/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.770: Device reported enroll progress, reported 15 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.770: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.770: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.770: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.770: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.770: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.771: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.771: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.771: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.771: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.771: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.771: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.771: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.771: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.772: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.772: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.772: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.772: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.772: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.772: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.772: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.772: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.772: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.772: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.772: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.773: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.773: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.773: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.773: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.773: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.773: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.773: Partial capture successful. Please touch the sensor again (16/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.773: Device reported enroll progress, reported 16 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.773: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.773: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.773: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.773: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.773: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.774: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.774: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.774: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.774: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.774: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.774: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.774: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.774: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.775: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.775: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.775: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.775: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.775: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.775: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.775: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.775: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.775: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.775: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.775: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.775: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.776: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.776: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.776: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.776: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.776: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.776: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.776: Partial capture successful. Please touch the sensor again (17/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.776: Device reported enroll progress, reported 17 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.776: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.776: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.776: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.776: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.776: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.777: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.777: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.777: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.777: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.777: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.777: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.777: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.777: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.778: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.778: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.778: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.778: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.778: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.778: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.778: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.778: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.778: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.778: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.778: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.778: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.779: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.779: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.779: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.779: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.779: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.779: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.779: Partial capture successful. Please touch the sensor again (18/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.779: Device reported enroll progress, reported 18 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.779: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.779: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.779: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.779: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.779: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.780: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.780: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.780: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.780: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.780: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.780: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.780: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.780: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.781: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.781: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.781: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.781: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.781: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.781: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.781: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.781: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.781: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.781: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.781: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.781: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.782: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.782: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.782: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.782: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.782: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.782: Partial capture successful. Please touch the sensor again (19/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.782: Device reported enroll progress, reported 19 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.782: [egismoc] ENROLL_STATES entering state 8 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.782: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.782: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.782: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.782: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.783: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.783: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.783: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.783: [egismoc] ENROLL_STATES entering state 9 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.783: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.783: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.783: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.783: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.784: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.784: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.784: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.784: [egismoc] ENROLL_STATES entering state 10 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.784: Wait for finger on sensor 135s (process:3963): libfprint-device-DEBUG: 20:25:43.784: Device reported finger status change: FP_FINGER_STATUS_NEEDED 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.784: Finger on sensor callback 135s (process:3963): libfprint-device-DEBUG: 20:25:43.784: Device reported finger status change: FP_FINGER_STATUS_PRESENT 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.784: [egismoc] ENROLL_STATES entering state 11 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.784: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.784: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.784: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.784: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.785: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.785: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.785: Read capture callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.785: Response prefix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.785: Response suffix valid: yes 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.785: Partial capture successful. Please touch the sensor again (20/20) 135s (process:3963): libfprint-device-DEBUG: 20:25:43.785: Device reported enroll progress, reported 20 of 20 have been completed 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.785: [egismoc] ENROLL_STATES entering state 12 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.785: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.785: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.785: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.785: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.786: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.786: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.786: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.786: [egismoc] ENROLL_STATES entering state 13 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.786: New fingerprint ID: FP1-00000000-7-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.786: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.786: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.786: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.786: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] ENROLL_STATES entering state 14 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Task SSM next state callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] ENROLL_STATES entering state 15 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Enrollment was successful! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.787: Device reported enroll completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.787: Device reported finger status change: FP_FINGER_STATUS_NONE 135s (process:3963): libfprint-device-DEBUG: 20:25:43.787: Print for finger FP_FINGER_RIGHT_INDEX enrolled 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] ENROLL_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.787: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.787: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: List 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] LIST_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.787: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.787: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.788: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.788: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Device fingerprint 2: FP1-00000000-7-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Number of currently enrolled fingerprints on the device is 2 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.788: [egismoc] LIST_STATES entering state 1 135s (process:3963): libfprint-device-DEBUG: 20:25:43.788: Device reported listing completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.788: [egismoc] LIST_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.788: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.788: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Delete 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.788: [egismoc] DELETE_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.788: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.788: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.789: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.789: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.789: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.789: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.789: Device fingerprint 1: FP1-00000000-2-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.789: Device fingerprint 2: FP1-00000000-7-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.789: Number of currently enrolled fingerprints on the device is 2 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.790: [egismoc] DELETE_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Get delete command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.790: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.790: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.790: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Delete callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Response prefix valid: yes 135s (process:3963): libfprint-device-DEBUG: 20:25:43.790: Device reported deletion completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.790: [egismoc] DELETE_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.790: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.790: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: List 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.790: [egismoc] LIST_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.790: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.790: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.791: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.791: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: Device fingerprint 1: FP1-00000000-7-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.791: [egismoc] LIST_STATES entering state 1 135s (process:3963): libfprint-device-DEBUG: 20:25:43.791: Device reported listing completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.791: [egismoc] LIST_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.791: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.791: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: Clear storage 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.791: [egismoc] DELETE_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.791: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.791: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.792: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.792: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.792: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.792: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.792: Device fingerprint 1: FP1-00000000-7-00000000-nobody 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.792: Number of currently enrolled fingerprints on the device is 1 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.792: [egismoc] DELETE_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.792: Get delete command 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.792: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.792: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.792: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.793: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.793: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.793: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.793: Delete callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.793: Response prefix valid: yes 135s (process:3963): libfprint-device-DEBUG: 20:25:43.793: Device reported deletion completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.793: [egismoc] DELETE_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.793: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.793: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.793: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.793: List 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.793: [egismoc] LIST_STATES entering state 0 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.793: Execute command and get response 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.793: Get check bytes 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.793: [egismoc] CMD_STATES entering state 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.793: [egismoc] CMD_STATES entering state 1 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.794: Command receive callback 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.794: [egismoc] CMD_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.794: List callback 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.794: Number of currently enrolled fingerprints on the device is 0 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.794: [egismoc] LIST_STATES entering state 1 135s (process:3963): libfprint-device-DEBUG: 20:25:43.794: Device reported listing completion 135s (process:3963): libfprint-SSM-DEBUG: 20:25:43.794: [egismoc] LIST_STATES completed successfully 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.794: Task SSM done 135s (process:3963): libfprint-device-DEBUG: 20:25:43.794: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.794: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.794: Closing device 135s (process:3963): libfprint-egismoc-DEBUG: 20:25:43.794: Cancel 135s (process:3963): libfprint-device-DEBUG: 20:25:43.794: Device reported close completion 135s (process:3963): libfprint-device-DEBUG: 20:25:43.794: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s (process:3963): libfprint-device-DEBUG: 20:25:43.794: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 8, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 9, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 10, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 11, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 12, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 13, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 14, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 15, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 16, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 17, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 18, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 19, , None, None) 135s finger status: 135s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x7756f5765f80 (FpiDeviceEgisMoc at 0x205ba950)>, 20, , None, None) 135s enroll new finger done 135s listing - device should have 2 prints 135s deleting first print 135s delete done 135s listing - device should only have second print 135s clear device storage 135s clear done 135s listing - device should be empty 135s ** (umockdev-run:3959): DEBUG: 20:25:43.811: umockdev.vala:154: Removing test bed /tmp/umockdev.ADV912 135s (umockdev-run:3959): GLib-DEBUG: 20:25:43.817: unsetenv() is not thread-safe and should not be used after threads are created 135s PASS: libfprint-2/driver-egismoc-0586.test 135s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.5.test 135s TAP version 14 135s # random seed: R02S5e32114fdbbb2febfc972f9d18ce7c97 135s 1..4 135s # Start of context tests 135s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 135s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 135s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b291f99f53b, GType is 108850046992176 135s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 135s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.5 135s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 135s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b291f98a987, GType is 108850046996976 135s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 135s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.5 135s ok 1 /context/new 135s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 135s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 135s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 135s ok 2 /context/no-devices 135s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 135s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 135s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b291f99f53b, GType is 108850046992176 135s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 135s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 135s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b291f98a987, GType is 108850046996976 135s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 135s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 135s # libfprint-context-DEBUG: created 135s # libfprint-device-DEBUG: Device reported probe completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 3 /context/has-virtual-device 135s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 135s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 135s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b291f99f53b, GType is 108850046992176 135s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 135s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 135s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b291f98a987, GType is 108850046996976 135s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 135s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 135s # libfprint-context-DEBUG: created 135s # libfprint-device-DEBUG: Device reported probe completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 4 /context/enumerates-new-devices 135s # End of context tests 135s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.5.test 135s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.1.test 135s (process:3981): libfprint-context-DEBUG: 20:25:43.843: Initializing FpContext (libfprint version 1.94.8+tod1) 135s (process:3981): libfprint-tod-DEBUG: 20:25:43.843: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 135s (process:3981): libfprint-tod-DEBUG: 20:25:43.843: Found TOD entry point symbol 0x77407d3069d3, GType is 94239813477184 135s (process:3981): libfprint-tod-DEBUG: 20:25:43.843: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 135s (process:3981): libfprint-tod-DEBUG: 20:25:43.843: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 135s (process:3981): libfprint-tod-DEBUG: 20:25:43.843: Found TOD entry point symbol 0x77407d300b7b, GType is 94239813487200 135s (process:3981): libfprint-tod-DEBUG: 20:25:43.843: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 135s (process:3981): libfprint-context-DEBUG: 20:25:43.844: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 135s (process:3981): libfprint-context-DEBUG: 20:25:43.844: created 135s (process:3981): libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: 20:25:43.844: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 135s 135s (process:3981): libfprint-device-DEBUG: 20:25:43.844: Device reported probe completion 135s (process:3981): libfprint-device-DEBUG: 20:25:43.844: Completing action FPI_DEVICE_ACTION_PROBE in idle! 135s (process:3981): libfprint-device-DEBUG: 20:25:43.844: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:3981): GLib-DEBUG: 20:25:43.844: setenv()/putenv() are not thread-safe and should not be used after threads are created 135s TAP version 14 135s # random seed: R02Sb22577f316069d89c60ba36a16b2ad0e 135s 1..97 135s # Start of driver tests 135s ok 1 /driver/get_driver 135s ok 2 /driver/get_device_id 135s ok 3 /driver/get_name 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 4 /driver/is_open 135s ok 5 /driver/get_nr_enroll_stages 135s ok 6 /driver/set_nr_enroll_stages 135s ok 7 /driver/supports_identify 135s ok 8 /driver/supports_capture 135s ok 9 /driver/has_storage 135s ok 10 /driver/do_not_support_identify 135s ok 11 /driver/do_not_support_capture 135s ok 12 /driver/has_not_storage 135s ok 13 /driver/get_usb_device 135s ok 14 /driver/get_virtual_env 135s ok 15 /driver/get_driver_data 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 135s # 135s # libfprint-device-DEBUG: Device reported probe completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 135s ok 16 /driver/initial_features 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 135s # 135s # libfprint-device-DEBUG: Device reported probe completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 17 /driver/probe 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 18 /driver/open 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 19 /driver/close 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 135s # 135s # libfprint-device-DEBUG: Device reported enroll completion 135s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 20 /driver/enroll 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 135s # 135s # libfprint-device-DEBUG: Device reported verify result 135s # libfprint-device-DEBUG: Device reported verify completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 21 /driver/verify 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 135s # 135s # libfprint-device-DEBUG: Device reported identify result 135s # libfprint-device-DEBUG: Device reported identify completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 22 /driver/identify 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 135s # 135s # libfprint-device-DEBUG: Device reported capture completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 23 /driver/capture 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 135s # 135s # libfprint-device-DEBUG: Device reported listing completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 24 /driver/list 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 25 /driver/delete 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 26 /driver/clear_storage 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 135s # 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 135s # 135s # libfprint-device-DEBUG: Device reported deletion completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s ok 27 /driver/cancel 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 135s # 135s # libfprint-device-DEBUG: Device reported open completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 135s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 135s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 135s # 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 135s # 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 135s # 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 135s # 135s # libfprint-device-DEBUG: Device reported verify result 135s # libfprint-device-DEBUG: Device reported verify completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 135s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 135s # 135s # libfprint-device-DEBUG: Device reported close completion 135s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 135s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 135s ok 28 /driver/critical 135s ok 29 /driver/get_current_action 136s ok 30 /driver/timeout 136s ok 31 /driver/error_types 136s ok 32 /driver/retry_error_types 136s # Start of get_scan_type tests 136s ok 33 /driver/get_scan_type/press 136s ok 34 /driver/get_scan_type/swipe 136s # End of get_scan_type tests 136s # Start of set_scan_type tests 136s ok 35 /driver/set_scan_type/press 136s ok 36 /driver/set_scan_type/swipe 136s # End of set_scan_type tests 136s # Start of finger_status tests 136s ok 37 /driver/finger_status/inactive 136s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s ok 38 /driver/finger_status/waiting 136s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s ok 39 /driver/finger_status/present 136s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 136s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 136s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 136s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 136s ok 40 /driver/finger_status/changes 136s # End of finger_status tests 136s # Start of features tests 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 136s # 136s # libfprint-device-DEBUG: Device reported probe completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 41 /driver/features/probe_updates 136s # End of features tests 136s # Start of initial_features tests 136s ok 42 /driver/initial_features/none 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s ok 43 /driver/initial_features/no_capture 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s ok 44 /driver/initial_features/no_verify 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s ok 45 /driver/initial_features/no_identify 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s ok 46 /driver/initial_features/no_storage 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s ok 47 /driver/initial_features/no_list 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s ok 48 /driver/initial_features/no_delete 136s ok 49 /driver/initial_features/no_clear 136s # End of initial_features tests 136s # Start of probe tests 136s # libfprint-device-DEBUG: Device reported probe completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 50 /driver/probe/error 136s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 136s # libfprint-device-DEBUG: Device reported probe completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 51 /driver/probe/action_error 136s # End of probe tests 136s # Start of open tests 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 52 /driver/open/error 136s # End of open tests 136s # Start of close tests 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 53 /driver/close/error 136s # End of close tests 136s # Start of enroll tests 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 136s # 136s # libfprint-device-DEBUG: Device reported enroll completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 54 /driver/enroll/error 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported enroll progress, reported 1880240137 of 1858122826 have been completed 136s # libfprint-device-DEBUG: Device reported enroll progress, reported 1962294513 of 1858122826 have been completed 136s # libfprint-device-DEBUG: Device reported enroll progress, reported 1878625912 of 1858122826 have been completed 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 136s # 136s # libfprint-device-DEBUG: Device reported enroll completion 136s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 55 /driver/enroll/progress 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 136s # 136s # libfprint-device-DEBUG: Device reported enroll completion 136s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 56 /driver/enroll/update_nbis 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 57 /driver/enroll/update_nbis_wrong_device 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 58 /driver/enroll/update_nbis_wrong_driver 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 59 /driver/enroll/update_nbis_missing_feature 136s # Start of error tests 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported enroll completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Device reported enroll completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Device reported enroll completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 60 /driver/enroll/error/no_print 136s # End of error tests 136s # End of enroll tests 136s # Start of verify tests 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 136s # 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 61 /driver/verify/fail 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 136s # 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 62 /driver/verify/retry 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 136s # 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 63 /driver/verify/error 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 64 /driver/verify/not_supported 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 65 /driver/verify/report_no_cb 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 66 /driver/verify/not_reported 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Device reported verify result 136s # libfprint-device-DEBUG: Device reported verify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 67 /driver/verify/complete_retry 136s # End of verify tests 136s # Start of identify tests 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 136s ok 68 /driver/identify/fail 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 69 /driver/identify/retry 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 136s ok 70 /driver/identify/error 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 71 /driver/identify/not_reported 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 72 /driver/identify/complete_retry 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 73 /driver/identify/report_no_cb 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 74 /driver/identify/suspend_continues 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-device-DEBUG: Device reported identify result 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 75 /driver/identify/suspend_succeeds 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 136s # 136s # libfprint-device-DEBUG: Device reported identify completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 136s ok 76 /driver/identify/suspend_busy_error 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 136s # 136s # libfprint-device-DEBUG: Device reported close completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s ok 77 /driver/identify/suspend_while_idle 136s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 136s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 136s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 136s # 136s # libfprint-device-DEBUG: Device reported open completion 136s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 136s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 138s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 138s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 138s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 138s # 138s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 138s # 138s # libfprint-device-DEBUG: Device reported identify completion 138s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 138s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 138s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 138s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 139s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.1.test 140s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 78 /driver/identify/warmup_cooldown 143s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 143s # End of identify tests 143s # Start of capture tests 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 79 /driver/capture/not_supported 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 143s # 143s # libfprint-device-DEBUG: Device reported capture completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s ok 80 /driver/capture/error 143s # End of capture tests 143s # Start of list tests 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 143s # 143s # libfprint-device-DEBUG: Device reported listing completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 81 /driver/list/error 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 82 /driver/list/no_storage 143s # End of list tests 143s # Start of delete tests 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 143s # 143s # libfprint-device-DEBUG: Device reported deletion completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 83 /driver/delete/error 143s # End of delete tests 143s # Start of clear_storage tests 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 143s # 143s # libfprint-device-DEBUG: Device reported deletion completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 84 /driver/clear_storage/error 143s # End of clear_storage tests 143s # Start of cancel tests 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 143s # 143s # libfprint-device-DEBUG: Device reported deletion completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 85 /driver/cancel/fail 143s # End of cancel tests 143s # Start of get_current_action tests 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 86 /driver/get_current_action/open 143s # End of get_current_action tests 143s # Start of get_cancellable tests 143s ok 87 /driver/get_cancellable/error 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 88 /driver/get_cancellable/open 143s # Start of open tests 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 89 /driver/get_cancellable/open/internal 143s # End of open tests 143s # End of get_cancellable tests 143s # Start of action_is_cancelled tests 143s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 90 /driver/action_is_cancelled/open 143s ok 91 /driver/action_is_cancelled/error 143s # Start of open tests 143s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s ok 92 /driver/action_is_cancelled/open/internal 143s # End of open tests 143s # End of action_is_cancelled tests 143s # Start of complete_action tests 143s # Start of all tests 143s ok 93 /driver/complete_action/all/error 143s # End of all tests 143s # End of complete_action tests 143s # Start of action_error tests 143s ok 94 /driver/action_error/error 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 143s # libfprint-device-DEBUG: Device reported enroll completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 143s # libfprint-device-DEBUG: Device reported verify completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 143s # libfprint-device-DEBUG: Device reported identify completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 143s # libfprint-device-DEBUG: Device reported capture completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 143s # libfprint-device-DEBUG: Device reported listing completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 143s # libfprint-device-DEBUG: Device reported deletion completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 143s # libfprint-device-DEBUG: Device reported deletion completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s ok 95 /driver/action_error/all 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 143s # 143s # libfprint-device-DEBUG: Device reported open completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 143s # 143s # libfprint-device-DEBUG: Device reported enroll completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 143s # 143s # libfprint-device-DEBUG: Device reported verify completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 143s # 143s # libfprint-device-DEBUG: Device reported identify completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 143s # 143s # libfprint-device-DEBUG: Device reported capture completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 143s # 143s # libfprint-device-DEBUG: Device reported listing completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 143s # 143s # libfprint-device-DEBUG: Device reported deletion completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.1' 143s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.1' 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 143s # 143s # libfprint-device-DEBUG: Device reported deletion completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 143s # 143s # libfprint-device-DEBUG: Device reported close completion 143s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s ok 96 /driver/action_error/fail 143s # End of action_error tests 143s # Start of timeout tests 143s ok 97 /driver/timeout/cancelled 143s # End of timeout tests 143s # End of driver tests 143s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.1.test 143s Running test: libfprint-2/driver-upektc_img-tcs1s.test 143s ** (umockdev-run:3989): DEBUG: 20:25:51.372: umockdev.vala:127: Created udev test bed /tmp/umockdev.CP6612 143s ** (umockdev-run:3989): DEBUG: 20:25:51.373: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 143s ** (umockdev-run:3989): DEBUG: 20:25:51.376: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 143s ** (umockdev-run:3989): DEBUG: 20:25:51.380: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CP6612/dev/bus/usb/003/004 143s ** (umockdev-run:3989): DEBUG: 20:25:51.380: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 143s ** (umockdev-run:3989): DEBUG: 20:25:51.383: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 143s ** (umockdev-run:3989): DEBUG: 20:25:51.386: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CP6612/dev/bus/usb/003/001 143s ** (umockdev-run:3989): DEBUG: 20:25:51.386: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 143s ** (umockdev-run:3989): DEBUG: 20:25:51.387: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 143s ** (umockdev-run:3989): DEBUG: 20:25:51.391: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1 143s ** (umockdev-run:3989): DEBUG: 20:25:51.391: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 143s (process:3993): libfprint-context-DEBUG: 20:25:51.472: Initializing FpContext (libfprint version 1.94.8+tod1) 143s (process:3993): libfprint-tod-DEBUG: 20:25:51.472: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 143s (process:3993): libfprint-context-DEBUG: 20:25:51.474: No driver found for USB device 1D6B:0002 143s (process:3993): libfprint-device-DEBUG: 20:25:51.475: Device reported probe completion 143s (process:3993): libfprint-device-DEBUG: 20:25:51.475: Completing action FPI_DEVICE_ACTION_PROBE in idle! 143s (process:3993): libfprint-device-DEBUG: 20:25:51.475: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.476: Image device open completed 143s (process:3993): libfprint-device-DEBUG: 20:25:51.476: Device reported open completion 143s (process:3993): libfprint-device-DEBUG: 20:25:51.476: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s (process:3993): libfprint-device-DEBUG: 20:25:51.476: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:3993): libfprint-device-DEBUG: 20:25:51.476: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.476: Activating image device 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.476: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.476: [upektc_img] ACTIVATE_NUM_STATES entering state 0 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.477: [upektc_img] ACTIVATE_NUM_STATES entering state 1 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.477: [upektc_img] ACTIVATE_NUM_STATES entering state 2 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.477: [upektc_img] ACTIVATE_NUM_STATES entering state 3 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.478: [upektc_img] ACTIVATE_NUM_STATES entering state 4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.478: [upektc_img] ACTIVATE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.479: [upektc_img] ACTIVATE_NUM_STATES entering state 6 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.479: [upektc_img] ACTIVATE_NUM_STATES entering state 7 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.479: [upektc_img] ACTIVATE_NUM_STATES entering state 8 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.480: [upektc_img] ACTIVATE_NUM_STATES entering state 9 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.480: [upektc_img] ACTIVATE_NUM_STATES entering state 10 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.480: [upektc_img] ACTIVATE_NUM_STATES entering state 11 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.481: Sensor type : TCS1x, width x height: 256 x 360 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.481: [upektc_img] ACTIVATE_NUM_STATES completed successfully 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.481: Image device activation completed 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.481: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.481: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 143s (process:3993): libfprint-device-DEBUG: 20:25:51.481: Device reported finger status change: FP_FINGER_STATUS_NEEDED 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.481: [upektc_img] CAPTURE_NUM_STATES entering state 0 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.481: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.482: request completed, len: 0000 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.482: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.482: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.482: 18th byte is 0c 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.482: [upektc_img] CAPTURE_NUM_STATES entering state 3 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.482: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.483: request completed, len: 0000 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.483: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.483: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.483: 18th byte is 13 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.483: [upektc_img] CAPTURE_NUM_STATES entering state 3 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.484: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.484: request completed, len: 0000 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.484: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.484: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.484: 18th byte is 00 143s (process:3993): libfprint-device-DEBUG: 20:25:51.484: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.484: [upektc_img] CAPTURE_NUM_STATES entering state 3 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.485: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.485: request completed, len: 0000 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.485: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.485: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.485: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.485: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.485: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.486: request completed, len: 07c4 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.486: Image device reported finger status: on 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.486: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.486: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.486: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.487: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.487: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.487: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.487: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.487: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.487: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.487: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.488: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.488: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.488: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.488: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.488: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.488: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.489: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.489: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.489: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.489: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.489: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.489: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.489: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.490: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.490: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.490: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.490: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.490: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.491: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.491: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.491: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.491: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.491: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.491: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.491: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.492: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.492: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.492: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.492: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.492: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.493: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.493: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.493: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.493: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.493: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.494: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.494: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.494: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.494: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.494: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.494: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.494: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.495: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.495: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.495: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.495: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.495: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.495: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.496: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.496: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.496: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.496: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.496: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.496: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.496: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.497: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.497: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.497: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.497: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.497: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.498: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.498: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.498: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.499: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.499: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.499: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.499: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.499: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.499: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.499: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.500: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.500: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.500: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.500: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.500: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.500: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.501: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.501: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.501: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.501: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.501: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.501: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.501: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.502: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.502: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.502: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.502: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.502: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.502: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.502: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.503: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.503: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.503: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.503: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.503: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.504: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.504: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.504: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.504: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.504: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.504: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.504: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.505: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.505: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.505: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.506: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.506: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.506: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.506: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.506: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.506: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.506: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.507: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.507: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.507: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.507: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.507: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.507: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.507: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.508: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.508: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.508: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.508: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.508: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.508: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.509: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.509: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.509: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.509: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.509: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.509: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.509: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.510: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.510: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.510: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.510: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.510: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.511: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.511: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.511: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.511: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.511: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.511: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.511: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.512: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.512: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.512: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.512: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.512: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.512: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.512: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.513: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.513: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.513: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.514: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.514: response_size is 2052, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.514: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.514: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.514: request completed, len: 07c4 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.514: [upektc_img] CAPTURE_NUM_STATES entering state 5 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.514: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.515: request completed, len: 0040 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.515: response_size is 814, actual_length is 64 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.515: Waiting for rest of transfer 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.515: [upektc_img] CAPTURE_NUM_STATES entering state 1 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.515: request completed, len: 02ee 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.515: Image size is 51840 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.515: Image device captured an image 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.515: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 143s (process:3993): libfprint-device-DEBUG: 20:25:51.516: Device reported finger status change: FP_FINGER_STATUS_PRESENT 143s (process:3993): libfprint-device-DEBUG: 20:25:51.516: Device reported finger status change: FP_FINGER_STATUS_NONE 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.516: Image device reported finger status: off 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.516: Deactivating image device 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.516: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.516: [upektc_img] CAPTURE_NUM_STATES completed successfully 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.516: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.516: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 143s (process:3993): libfprint-SSM-DEBUG: 20:25:51.517: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 143s (process:3993): libfprint-upektc_img-DEBUG: 20:25:51.517: Deactivate completed 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.517: Image device deactivation completed 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.517: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 143s (process:3993): libfprint-image-DEBUG: 20:25:51.529: Minutiae scan completed in 0.013650 secs 143s (process:3993): libfprint-device-DEBUG: 20:25:51.529: Device reported capture completion 143s (process:3993): libfprint-device-DEBUG: 20:25:51.529: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 143s (process:3993): libfprint-device-DEBUG: 20:25:51.529: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 143s (process:3993): libfprint-image_device-DEBUG: 20:25:51.530: Image device close completed 143s (process:3993): libfprint-device-DEBUG: 20:25:51.530: Device reported close completion 143s (process:3993): libfprint-device-DEBUG: 20:25:51.530: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s (process:3993): libfprint-device-DEBUG: 20:25:51.530: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s ** (umockdev-run:3989): DEBUG: 20:25:51.603: umockdev.vala:154: Removing test bed /tmp/umockdev.CP6612 143s (umockdev-run:3989): GLib-DEBUG: 20:25:51.610: unsetenv() is not thread-safe and should not be used after threads are created 143s Comparing PNGs /tmp/libfprint-umockdev-test-jf642aeg/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 143s PASS: libfprint-2/driver-upektc_img-tcs1s.test 143s Running test: libfprint-2/driver-uru4000-4500.test 143s ** (umockdev-run:4002): DEBUG: 20:25:51.671: umockdev.vala:127: Created udev test bed /tmp/umockdev.H5SE22 143s ** (umockdev-run:4002): DEBUG: 20:25:51.671: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 143s ** (umockdev-run:4002): DEBUG: 20:25:51.672: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 143s ** (umockdev-run:4002): DEBUG: 20:25:51.675: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.H5SE22/dev/bus/usb/001/050 143s ** (umockdev-run:4002): DEBUG: 20:25:51.675: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 143s ** (umockdev-run:4002): DEBUG: 20:25:51.676: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 143s ** (umockdev-run:4002): DEBUG: 20:25:51.679: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.H5SE22/dev/bus/usb/001/001 143s ** (umockdev-run:4002): DEBUG: 20:25:51.679: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 143s ** (umockdev-run:4002): DEBUG: 20:25:51.679: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 143s (process:4006): libfprint-context-DEBUG: 20:25:51.755: Initializing FpContext (libfprint version 1.94.8+tod1) 143s (process:4006): libfprint-tod-DEBUG: 20:25:51.755: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 143s (process:4006): libfprint-context-DEBUG: 20:25:51.757: No driver found for USB device 1D6B:0002 143s (process:4006): libfprint-device-DEBUG: 20:25:51.757: Device reported probe completion 143s (process:4006): libfprint-device-DEBUG: 20:25:51.757: Completing action FPI_DEVICE_ACTION_PROBE in idle! 143s (process:4006): libfprint-device-DEBUG: 20:25:51.758: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:4006): GLib-DEBUG: 20:25:51.759: setenv()/putenv() are not thread-safe and should not be used after threads are created 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.766: Image device open completed 143s (process:4006): libfprint-device-DEBUG: 20:25:51.766: Device reported open completion 143s (process:4006): libfprint-device-DEBUG: 20:25:51.766: Completing action FPI_DEVICE_ACTION_OPEN in idle! 143s (process:4006): libfprint-device-DEBUG: 20:25:51.766: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:4006): libfprint-device-DEBUG: 20:25:51.766: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.767: Activating image device 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.767: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.767: [uru4000] INIT_NUM_STATES entering state 0 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.767: read 1 regs at 7 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.768: reg value 1 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.768: [uru4000] INIT_NUM_STATES entering state 1 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.768: [uru4000] INIT_NUM_STATES entering state 3 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.768: set 81 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.769: [uru4000] INIT_NUM_STATES entering state 4 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.769: [uru4000] POWERUP_NUM_STATES entering state 0 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.769: [uru4000] POWERUP_NUM_STATES entering state 1 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.769: set 01 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.769: recv irq type 56aa 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.769: early scanpwr interrupt 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.769: [uru4000] POWERUP_NUM_STATES entering state 2 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.769: read 1 regs at 7 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.770: reg value 1 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.770: [uru4000] POWERUP_NUM_STATES entering state 3 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.770: [uru4000] POWERUP_NUM_STATES completed successfully 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.770: [uru4000] INIT_NUM_STATES entering state 5 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.770: [uru4000] INIT_NUM_STATES entering state 6 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.770: [uru4000] INIT_NUM_STATES entering state 7 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.770: read 16 regs at f0 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.770: reg value 1a 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.770: [uru4000] INIT_NUM_STATES entering state 8 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.770: Versions 0010 and 0115 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.770: [uru4000] INIT_NUM_STATES completed successfully 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.770: Image device activation completed 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.770: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.770: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.770: wait finger on 143s (process:4006): libfprint-device-DEBUG: 20:25:51.771: Device reported finger status change: FP_FINGER_STATUS_NEEDED 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.771: recv irq type 56aa 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.772: recv irq type 56aa 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.772: recv irq type 0101 143s (process:4006): libfprint-device-DEBUG: 20:25:51.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.772: Image device reported finger status: on 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.772: starting capture 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.772: Image encryption seed: 1374298404 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.772: [uru4000] IMAGING_NUM_STATES entering state 0 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.774: [uru4000] IMAGING_NUM_STATES entering state 1 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.774: hw header lines 289 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.774: dev2: 11240 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.774: image seems to be encrypted 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.774: [uru4000] IMAGING_NUM_STATES entering state 2 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: read 4 regs at 34 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: reg value f2 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.775: [uru4000] IMAGING_NUM_STATES entering state 3 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: encryption id 00 -> key 544409d6 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 0 02 72 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: decoding 72 lines 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 1 00 1 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: skipping 1 lines 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 2 02 49 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: decoding 49 lines 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 3 01 1 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: skipping 1 lines 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 4 00 1 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: skipping 1 lines 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 5 02 49 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: decoding 49 lines 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 6 00 1 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: skipping 1 lines 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: 7 02 116 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.775: decoding 116 lines 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.776: [uru4000] IMAGING_NUM_STATES entering state 4 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.776: Image device captured an image 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.776: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 143s (process:4006): libfprint-device-DEBUG: 20:25:51.777: Device reported finger status change: FP_FINGER_STATUS_PRESENT 143s (process:4006): libfprint-SSM-DEBUG: 20:25:51.777: [uru4000] IMAGING_NUM_STATES completed successfully 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.777: await finger off 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.778: recv irq type 0200 143s (process:4006): libfprint-device-DEBUG: 20:25:51.778: Device reported finger status change: FP_FINGER_STATUS_NONE 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.778: Image device reported finger status: off 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.778: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.778: Deactivating image device 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.778: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.778: deactivating 143s (process:4006): libfprint-uru4000-DEBUG: 20:25:51.779: cancelled 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.779: Image device deactivation completed 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.779: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 143s (process:4006): libfprint-image-DEBUG: 20:25:51.793: Minutiae scan completed in 0.016271 secs 143s (process:4006): libfprint-device-DEBUG: 20:25:51.793: Device reported capture completion 143s (process:4006): libfprint-device-DEBUG: 20:25:51.793: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 143s (process:4006): libfprint-device-DEBUG: 20:25:51.793: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 143s (process:4006): libfprint-image_device-DEBUG: 20:25:51.793: Image device close completed 143s (process:4006): libfprint-device-DEBUG: 20:25:51.794: Device reported close completion 143s (process:4006): libfprint-device-DEBUG: 20:25:51.794: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 143s (process:4006): libfprint-device-DEBUG: 20:25:51.794: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 143s ** (umockdev-run:4002): DEBUG: 20:25:51.924: umockdev.vala:154: Removing test bed /tmp/umockdev.H5SE22 143s (umockdev-run:4002): GLib-DEBUG: 20:25:51.930: unsetenv() is not thread-safe and should not be used after threads are created 144s Comparing PNGs /tmp/libfprint-umockdev-test-k4g7yz1j/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 144s PASS: libfprint-2/driver-uru4000-4500.test 144s Running test: libfprint-2/fpi-ssm.test 144s TAP version 14 144s # random seed: R02S4d19e840173f9d1a1ef3a62d23d6f515 144s 1..42 144s # Start of ssm tests 144s ok 1 /ssm/new 144s ok 2 /ssm/set_data 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s ok 3 /ssm/start 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 4 /ssm/next 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 5 /ssm/jump_to_state 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 144s ok 6 /ssm/mark_completed 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # 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. 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 144s ok 7 /ssm/mark_failed 144s # Start of new tests 144s ok 8 /ssm/new/full 144s ok 9 /ssm/new/no_handler 144s ok 10 /ssm/new/wrong_states 144s # End of new tests 144s # Start of set_data tests 144s ok 11 /ssm/set_data/cleanup 144s # End of set_data tests 144s # Start of start tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 144s ok 12 /ssm/start/single 144s # End of start tests 144s # Start of next tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 144s ok 13 /ssm/next/complete 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 14 /ssm/next/not_started 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 15 /ssm/next/with_delayed 144s # End of next tests 144s # Start of jump_to_state tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 144s ok 16 /ssm/jump_to_state/not_started 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 144s ok 17 /ssm/jump_to_state/with_delayed 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 144s ok 18 /ssm/jump_to_state/last 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 144s ok 19 /ssm/jump_to_state/wrong 144s # End of jump_to_state tests 144s # Start of mark_completed tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 144s ok 20 /ssm/mark_completed/not_started 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 144s Executing: libfprint-2/fpi-ssm.test 144s ok 21 /ssm/mark_completed/with_delayed 144s # End of mark_completed tests 144s # Start of mark_failed tests 144s # 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. 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 144s ok 22 /ssm/mark_failed/not_started 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # 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. 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 144s ok 23 /ssm/mark_failed/with_delayed 144s # End of mark_failed tests 144s # Start of delayed tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 24 /ssm/delayed/next 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 25 /ssm/delayed/jump_to_state 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 144s ok 26 /ssm/delayed/mark_completed 144s # Start of next tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 144s ok 27 /ssm/delayed/next/cancel 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 28 /ssm/delayed/next/not_started 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 144s ok 29 /ssm/delayed/next/complete 144s # End of next tests 144s # Start of jump_to_state tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 144s ok 30 /ssm/delayed/jump_to_state/cancel 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 144s ok 31 /ssm/delayed/jump_to_state/not_started 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 144s ok 32 /ssm/delayed/jump_to_state/last 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 144s ok 33 /ssm/delayed/jump_to_state/wrong 144s # End of jump_to_state tests 144s # Start of mark_completed tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 144s ok 34 /ssm/delayed/mark_completed/cancel 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 144s ok 35 /ssm/delayed/mark_completed/not_started 144s # End of mark_completed tests 144s # Start of cancel tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 144s ok 36 /ssm/delayed/cancel/error 144s # End of cancel tests 144s # End of delayed tests 144s # Start of subssm tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 37 /ssm/subssm/start 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 144s # 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. 144s # 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. 144s # 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. 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 144s ok 38 /ssm/subssm/mark_failed 144s # Start of start tests 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 144s ok 39 /ssm/subssm/start/with_started 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 144s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 145s ok 40 /ssm/subssm/start/with_delayed 145s # End of start tests 145s # End of subssm tests 145s # Start of cleanup tests 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 145s ok 41 /ssm/cleanup/complete 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 145s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 145s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 145s ok 42 /ssm/cleanup/fail 145s # End of cleanup tests 145s # End of ssm tests 145s PASS: libfprint-2/fpi-ssm.test 145s Running test: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.94.1.test 145s TAP version 14 145s # random seed: R02S62aa86222cc082c400a8534a4dc70951 145s 1..4 145s # Start of context tests 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 145s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 145s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7272422c59d3, GType is 103591278914960 145s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 145s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 145s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7272422bfb7b, GType is 103591278919632 145s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 145s ok 1 /context/new 145s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 145s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 145s ok 2 /context/no-devices 145s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 145s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 145s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7272422c59d3, GType is 103591278914960 145s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 145s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 145s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7272422bfb7b, GType is 103591278919632 145s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 145s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 145s # libfprint-context-DEBUG: created 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM_SINGLE_STATE entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM_SINGLE_STATE completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 14 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state -10 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 14 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state -10 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed successfully 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 145s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: non-cleanup 146s # libfprint-device-DEBUG: Device reported probe completion 146s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 146s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 146s ok 3 /context/has-virtual-device 146s # slow test /context/has-virtual-device executed in 1.04 secs 146s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 146s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 146s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7272422c59d3, GType is 103591278914960 146s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 146s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 146s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7272422bfb7b, GType is 103591278919632 146s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 146s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 146s # libfprint-context-DEBUG: created 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM_SINGLE_STATE entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM_SINGLE_STATE completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 14 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state -10 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 14 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state -10 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 146s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM cancelled delayed state change 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 1 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed successfully 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed successfully 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed successfully 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 1 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed successfully 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 0 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 2 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM entering state 3 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 147s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.1] FPI_TEST_SSM completed with error: non-cleanup 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 4 /context/enumerates-new-devices 147s # slow test /context/enumerates-new-devices executed in 1.03 secs 147s # End of context tests 147s PASS: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.94.1.test 147s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.1.test 147s TAP version 14 147s # random seed: R02S3f7addccba2495ac9f2e7eb6a17ee421 147s 1..4 147s # Start of context tests 147s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 147s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 147s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7ac661ac3987, GType is 110330369486224 147s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 147s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.1 147s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 147s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7ac661abd53b, GType is 110330369491024 147s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 147s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.1 147s ok 1 /context/new 147s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 147s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 147s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 147s ok 2 /context/no-devices 147s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 147s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 147s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7ac661ac3987, GType is 110330369486224 147s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 147s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 147s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7ac661abd53b, GType is 110330369491024 147s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 147s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 147s # libfprint-context-DEBUG: created 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 3 /context/has-virtual-device 147s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 147s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 147s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7ac661ac3987, GType is 110330369486224 147s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 147s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 147s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7ac661abd53b, GType is 110330369491024 147s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 147s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 147s # libfprint-context-DEBUG: created 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 4 /context/enumerates-new-devices 147s # End of context tests 147s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.1.test 147s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.7.test 147s (process:4039): libfprint-context-DEBUG: 20:25:55.107: Initializing FpContext (libfprint version 1.94.8+tod1) 147s (process:4039): libfprint-tod-DEBUG: 20:25:55.107: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 147s (process:4039): libfprint-tod-DEBUG: 20:25:55.108: Found TOD entry point symbol 0x71f4f97b09d3, GType is 97668656964416 147s (process:4039): libfprint-tod-DEBUG: 20:25:55.108: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 147s (process:4039): libfprint-tod-DEBUG: 20:25:55.108: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 147s (process:4039): libfprint-tod-DEBUG: 20:25:55.108: Found TOD entry point symbol 0x71f4f97aab7b, GType is 97668656974432 147s (process:4039): libfprint-tod-DEBUG: 20:25:55.108: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 147s (process:4039): libfprint-context-DEBUG: 20:25:55.108: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 147s (process:4039): libfprint-context-DEBUG: 20:25:55.109: created 147s (process:4039): libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: 20:25:55.109: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 147s 147s (process:4039): libfprint-device-DEBUG: 20:25:55.109: Device reported probe completion 147s (process:4039): libfprint-device-DEBUG: 20:25:55.109: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s (process:4039): libfprint-device-DEBUG: 20:25:55.109: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:4039): GLib-DEBUG: 20:25:55.109: setenv()/putenv() are not thread-safe and should not be used after threads are created 147s TAP version 14 147s # random seed: R02S6562c346ea44c3dc4fda0e9bb64fe7b4 147s 1..97 147s # Start of driver tests 147s ok 1 /driver/get_driver 147s ok 2 /driver/get_device_id 147s ok 3 /driver/get_name 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 4 /driver/is_open 147s ok 5 /driver/get_nr_enroll_stages 147s ok 6 /driver/set_nr_enroll_stages 147s ok 7 /driver/supports_identify 147s ok 8 /driver/supports_capture 147s ok 9 /driver/has_storage 147s ok 10 /driver/do_not_support_identify 147s ok 11 /driver/do_not_support_capture 147s ok 12 /driver/has_not_storage 147s ok 13 /driver/get_usb_device 147s ok 14 /driver/get_virtual_env 147s ok 15 /driver/get_driver_data 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 147s # 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s ok 16 /driver/initial_features 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 147s # 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 17 /driver/probe 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 18 /driver/open 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 19 /driver/close 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 147s # 147s # libfprint-device-DEBUG: Device reported enroll completion 147s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 20 /driver/enroll 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 21 /driver/verify 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 22 /driver/identify 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 147s # 147s # libfprint-device-DEBUG: Device reported capture completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 23 /driver/capture 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 147s # 147s # libfprint-device-DEBUG: Device reported listing completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 24 /driver/list 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 147s # 147s # libfprint-device-DEBUG: Device reported deletion completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 25 /driver/delete 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 147s # 147s # libfprint-device-DEBUG: Device reported deletion completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 26 /driver/clear_storage 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 147s # 147s # libfprint-device-DEBUG: Device reported deletion completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 27 /driver/cancel 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 28 /driver/critical 147s ok 29 /driver/get_current_action 147s ok 30 /driver/timeout 147s ok 31 /driver/error_types 147s ok 32 /driver/retry_error_types 147s # Start of get_scan_type tests 147s ok 33 /driver/get_scan_type/press 147s ok 34 /driver/get_scan_type/swipe 147s # End of get_scan_type tests 147s # Start of set_scan_type tests 147s ok 35 /driver/set_scan_type/press 147s ok 36 /driver/set_scan_type/swipe 147s # End of set_scan_type tests 147s # Start of finger_status tests 147s ok 37 /driver/finger_status/inactive 147s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 147s ok 38 /driver/finger_status/waiting 147s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 147s ok 39 /driver/finger_status/present 147s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 147s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 147s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 147s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 147s ok 40 /driver/finger_status/changes 147s # End of finger_status tests 147s # Start of features tests 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 147s # 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 41 /driver/features/probe_updates 147s # End of features tests 147s # Start of initial_features tests 147s ok 42 /driver/initial_features/none 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s ok 43 /driver/initial_features/no_capture 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s ok 44 /driver/initial_features/no_verify 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s ok 45 /driver/initial_features/no_identify 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s ok 46 /driver/initial_features/no_storage 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s ok 47 /driver/initial_features/no_list 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s ok 48 /driver/initial_features/no_delete 147s ok 49 /driver/initial_features/no_clear 147s # End of initial_features tests 147s # Start of probe tests 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 50 /driver/probe/error 147s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 147s # libfprint-device-DEBUG: Device reported probe completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 51 /driver/probe/action_error 147s # End of probe tests 147s # Start of open tests 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 52 /driver/open/error 147s # End of open tests 147s # Start of close tests 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 53 /driver/close/error 147s # End of close tests 147s # Start of enroll tests 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 147s # 147s # libfprint-device-DEBUG: Device reported enroll completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 54 /driver/enroll/error 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported enroll progress, reported 1776496676 of 1046154743 have been completed 147s # libfprint-device-DEBUG: Device reported enroll progress, reported 1958380424 of 1046154743 have been completed 147s # libfprint-device-DEBUG: Device reported enroll progress, reported 1683421044 of 1046154743 have been completed 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 147s # 147s # libfprint-device-DEBUG: Device reported enroll completion 147s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 55 /driver/enroll/progress 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 147s # 147s # libfprint-device-DEBUG: Device reported enroll completion 147s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 56 /driver/enroll/update_nbis 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 57 /driver/enroll/update_nbis_wrong_device 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 58 /driver/enroll/update_nbis_wrong_driver 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 59 /driver/enroll/update_nbis_missing_feature 147s # Start of error tests 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported enroll completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Device reported enroll completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Device reported enroll completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 60 /driver/enroll/error/no_print 147s # End of error tests 147s # End of enroll tests 147s # Start of verify tests 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 61 /driver/verify/fail 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 62 /driver/verify/retry 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 147s # 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 63 /driver/verify/error 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 64 /driver/verify/not_supported 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 65 /driver/verify/report_no_cb 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 66 /driver/verify/not_reported 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Device reported verify result 147s # libfprint-device-DEBUG: Device reported verify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 67 /driver/verify/complete_retry 147s # End of verify tests 147s # Start of identify tests 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 147s ok 68 /driver/identify/fail 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 147s ok 69 /driver/identify/retry 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 147s ok 70 /driver/identify/error 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 71 /driver/identify/not_reported 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 72 /driver/identify/complete_retry 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 73 /driver/identify/report_no_cb 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 74 /driver/identify/suspend_continues 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-device-DEBUG: Device reported identify result 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 75 /driver/identify/suspend_succeeds 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 147s # 147s # libfprint-device-DEBUG: Device reported identify completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 147s ok 76 /driver/identify/suspend_busy_error 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 147s # 147s # libfprint-device-DEBUG: Device reported close completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s ok 77 /driver/identify/suspend_while_idle 147s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 147s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 147s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 147s # 147s # libfprint-device-DEBUG: Device reported open completion 147s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 147s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 149s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.7.test 149s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 149s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 149s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 149s # 149s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 149s # 149s # libfprint-device-DEBUG: Device reported identify completion 149s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 149s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 149s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 149s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 151s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 154s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.7.test 154s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 78 /driver/identify/warmup_cooldown 154s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 154s # End of identify tests 154s # Start of capture tests 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 79 /driver/capture/not_supported 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 154s # 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 80 /driver/capture/error 154s # End of capture tests 154s # Start of list tests 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 154s # 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 81 /driver/list/error 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 82 /driver/list/no_storage 154s # End of list tests 154s # Start of delete tests 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 83 /driver/delete/error 154s # End of delete tests 154s # Start of clear_storage tests 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 84 /driver/clear_storage/error 154s # End of clear_storage tests 154s # Start of cancel tests 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 85 /driver/cancel/fail 154s # End of cancel tests 154s # Start of get_current_action tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 86 /driver/get_current_action/open 154s # End of get_current_action tests 154s # Start of get_cancellable tests 154s ok 87 /driver/get_cancellable/error 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 88 /driver/get_cancellable/open 154s # Start of open tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 89 /driver/get_cancellable/open/internal 154s # End of open tests 154s # End of get_cancellable tests 154s # Start of action_is_cancelled tests 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 90 /driver/action_is_cancelled/open 154s ok 91 /driver/action_is_cancelled/error 154s # Start of open tests 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 92 /driver/action_is_cancelled/open/internal 154s # End of open tests 154s # End of action_is_cancelled tests 154s # Start of complete_action tests 154s # Start of all tests 154s ok 93 /driver/complete_action/all/error 154s # End of all tests 154s # End of complete_action tests 154s # Start of action_error tests 154s ok 94 /driver/action_error/error 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 95 /driver/action_error/all 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 154s # 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 154s # 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 154s # 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 154s # 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 154s # 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 154s # 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.94.7' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.94.7' 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 154s # 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-fake_test_dev_tod_v1+1.94.7-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 154s # 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 96 /driver/action_error/fail 154s # End of action_error tests 154s # Start of timeout tests 154s ok 97 /driver/timeout/cancelled 154s # End of timeout tests 154s # End of driver tests 154s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.94.7.test 154s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.5.test 154s (process:4045): libfprint-context-DEBUG: 20:26:02.613: Initializing FpContext (libfprint version 1.94.8+tod1) 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Found TOD entry point symbol 0x73a505a6053b, GType is 94766241428704 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Initializing features for driver fake_test_dev_tod_v1+1.90.5 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Found TOD entry point symbol 0x73a505a4b987, GType is 94766241438096 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 154s (process:4045): libfprint-tod-DEBUG: 20:26:02.614: Initializing features for driver ssm_test_dev_tod_v1+1.90.5 154s (process:4045): libfprint-context-DEBUG: 20:26:02.615: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 154s (process:4045): libfprint-context-DEBUG: 20:26:02.615: created 154s (process:4045): libfprint-device-DEBUG: 20:26:02.615: Device reported probe completion 154s (process:4045): libfprint-device-DEBUG: 20:26:02.616: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s (process:4045): libfprint-device-DEBUG: 20:26:02.616: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:4045): GLib-DEBUG: 20:26:02.616: setenv()/putenv() are not thread-safe and should not be used after threads are created 154s TAP version 14 154s # random seed: R02S9e9e929d66fe8a4e072c4a708a00ed5c 154s 1..97 154s # Start of driver tests 154s ok 1 /driver/get_driver 154s ok 2 /driver/get_device_id 154s ok 3 /driver/get_name 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 4 /driver/is_open 154s ok 5 /driver/get_nr_enroll_stages 154s ok 6 /driver/set_nr_enroll_stages 154s ok 7 /driver/supports_identify 154s ok 8 /driver/supports_capture 154s ok 9 /driver/has_storage 154s ok 10 /driver/do_not_support_identify 154s ok 11 /driver/do_not_support_capture 154s ok 12 /driver/has_not_storage 154s ok 13 /driver/get_usb_device 154s ok 14 /driver/get_virtual_env 154s ok 15 /driver/get_driver_data 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 16 /driver/initial_features 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 17 /driver/probe 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 18 /driver/open 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 19 /driver/close 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 20 /driver/enroll 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 21 /driver/verify 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 22 /driver/identify 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 23 /driver/capture 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 24 /driver/list 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 25 /driver/delete 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 26 /driver/clear_storage # SKIP Feature not supported by TODv1 versions before 1.92.0 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 27 /driver/cancel 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 28 /driver/critical # SKIP Feature not supported by TODv1 versions before 1.94.0 154s ok 29 /driver/get_current_action 154s ok 30 /driver/timeout 154s ok 31 /driver/error_types 154s ok 32 /driver/retry_error_types 154s # Start of get_scan_type tests 154s ok 33 /driver/get_scan_type/press 154s ok 34 /driver/get_scan_type/swipe 154s # End of get_scan_type tests 154s # Start of set_scan_type tests 154s ok 35 /driver/set_scan_type/press 154s ok 36 /driver/set_scan_type/swipe 154s # End of set_scan_type tests 154s # Start of finger_status tests 154s ok 37 /driver/finger_status/inactive 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 154s ok 38 /driver/finger_status/waiting 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 154s ok 39 /driver/finger_status/present 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 154s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 154s ok 40 /driver/finger_status/changes 154s # End of finger_status tests 154s # Start of features tests 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 41 /driver/features/probe_updates # SKIP Feature not supported by TODv1 versions before 1.92.0 154s # End of features tests 154s # Start of initial_features tests 154s ok 42 /driver/initial_features/none 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 43 /driver/initial_features/no_capture 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 44 /driver/initial_features/no_verify 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 45 /driver/initial_features/no_identify 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 46 /driver/initial_features/no_storage 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 47 /driver/initial_features/no_list 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 48 /driver/initial_features/no_delete 154s ok 49 /driver/initial_features/no_clear 154s # End of initial_features tests 154s # Start of probe tests 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 50 /driver/probe/error 154s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 154s # libfprint-device-DEBUG: Device reported probe completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 51 /driver/probe/action_error 154s # End of probe tests 154s # Start of open tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 52 /driver/open/error 154s # End of open tests 154s # Start of close tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 53 /driver/close/error 154s # End of close tests 154s # Start of enroll tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 54 /driver/enroll/error 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 2112617867 of 1139661444 have been completed 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 1468422692 of 1139661444 have been completed 154s # libfprint-device-DEBUG: Device reported enroll progress, reported 2110185860 of 1139661444 have been completed 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 55 /driver/enroll/progress 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 56 /driver/enroll/update_nbis 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 57 /driver/enroll/update_nbis_wrong_device 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 58 /driver/enroll/update_nbis_wrong_driver 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 59 /driver/enroll/update_nbis_missing_feature 154s # Start of error tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 60 /driver/enroll/error/no_print 154s # End of error tests 154s # End of enroll tests 154s # Start of verify tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 61 /driver/verify/fail 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 62 /driver/verify/retry 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 63 /driver/verify/error 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 64 /driver/verify/not_supported 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 65 /driver/verify/report_no_cb 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 66 /driver/verify/not_reported 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify result 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 67 /driver/verify/complete_retry 154s # End of verify tests 154s # Start of identify tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 68 /driver/identify/fail 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 69 /driver/identify/retry 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 70 /driver/identify/error 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 71 /driver/identify/not_reported 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 72 /driver/identify/complete_retry 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported identify result 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 73 /driver/identify/report_no_cb 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 74 /driver/identify/suspend_continues # SKIP Feature not supported by TODv1 versions before 1.94.0 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 75 /driver/identify/suspend_succeeds # SKIP Feature not supported by TODv1 versions before 1.94.0 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 76 /driver/identify/suspend_busy_error # SKIP Feature not supported by TODv1 versions before 1.94.0 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 77 /driver/identify/suspend_while_idle # SKIP Feature not supported by TODv1 versions before 1.94.0 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 78 /driver/identify/warmup_cooldown # SKIP Feature not supported by TODv1 versions before 1.94.0 154s # End of identify tests 154s # Start of capture tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 79 /driver/capture/not_supported 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 80 /driver/capture/error 154s # End of capture tests 154s # Start of list tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 81 /driver/list/error 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 82 /driver/list/no_storage 154s # End of list tests 154s # Start of delete tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 83 /driver/delete/error 154s # End of delete tests 154s # Start of clear_storage tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 84 /driver/clear_storage/error # SKIP Feature not supported by TODv1 versions before 1.92.0 154s # End of clear_storage tests 154s # Start of cancel tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 85 /driver/cancel/fail 154s # End of cancel tests 154s # Start of get_current_action tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 86 /driver/get_current_action/open 154s # End of get_current_action tests 154s # Start of get_cancellable tests 154s ok 87 /driver/get_cancellable/error 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 88 /driver/get_cancellable/open 154s # Start of open tests 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s ok 89 /driver/get_cancellable/open/internal 154s # End of open tests 154s # End of get_cancellable tests 154s # Start of action_is_cancelled tests 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 90 /driver/action_is_cancelled/open # SKIP Feature not supported by TODv1 versions before 1.94.0 154s ok 91 /driver/action_is_cancelled/error 154s # Start of open tests 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s ok 92 /driver/action_is_cancelled/open/internal # SKIP Feature not supported by TODv1 versions before 1.94.0 154s # End of open tests 154s # End of action_is_cancelled tests 154s # Start of complete_action tests 154s # Start of all tests 154s ok 93 /driver/complete_action/all/error 154s # End of all tests 154s # End of complete_action tests 154s # Start of action_error tests 154s ok 94 /driver/action_error/error 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 95 /driver/action_error/all 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported open completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 154s # libfprint-device-DEBUG: Device reported enroll completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported verify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported identify completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported capture completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported listing completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Device reported deletion completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version info is 'v1+1.90.5' 154s # libfprint-device-DEBUG: Tod version is '1', subversion '1.90.5' 154s # libfprint-device-DEBUG: Device reported close completion 154s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 154s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 154s ok 96 /driver/action_error/fail 154s # End of action_error tests 154s # Start of timeout tests 154s ok 97 /driver/timeout/cancelled 154s # End of timeout tests 154s # End of driver tests 154s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_v1+1.90.5.test 154s Running test: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.94.3.test 154s TAP version 14 154s # random seed: R02Sda987bf6861208436c98280cf02821b1 154s 1..4 154s # Start of context tests 154s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 154s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 154s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7422a15719d3, GType is 107795163622800 154s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 154s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 154s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7422a156bb7b, GType is 107795163627472 154s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 154s ok 1 /context/new 154s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 154s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 154s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 154s ok 2 /context/no-devices 154s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 154s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 154s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7422a15719d3, GType is 107795163622800 154s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 154s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 154s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7422a156bb7b, GType is 107795163627472 154s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 154s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 154s # libfprint-context-DEBUG: created 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM_SINGLE_STATE entering state 0 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM_SINGLE_STATE completed successfully 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 154s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 14 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state -10 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 14 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state -10 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: non-cleanup 155s # libfprint-device-DEBUG: Device reported probe completion 155s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 155s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 155s ok 3 /context/has-virtual-device 155s # slow test /context/has-virtual-device executed in 1.04 secs 155s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 155s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 155s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7422a15719d3, GType is 107795163622800 155s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 155s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 155s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7422a156bb7b, GType is 107795163627472 155s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 155s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 155s # libfprint-context-DEBUG: created 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM_SINGLE_STATE entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM_SINGLE_STATE completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 155s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 14 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state -10 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 14 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state -10 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM cancelled delayed state change 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed successfully 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 0 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 2 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM entering state 3 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 156s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.3] FPI_TEST_SSM completed with error: non-cleanup 156s # libfprint-device-DEBUG: Device reported probe completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 4 /context/enumerates-new-devices 156s # slow test /context/enumerates-new-devices executed in 1.04 secs 156s # End of context tests 156s PASS: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.94.3.test 156s Running test: libfprint-2/fpi-device.test 156s TAP version 14 156s # random seed: R02S941c963299a46921ec00245c0ae7d445 156s 1..97 156s # Start of driver tests 156s ok 1 /driver/get_driver 156s ok 2 /driver/get_device_id 156s ok 3 /driver/get_name 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 4 /driver/is_open 156s ok 5 /driver/get_nr_enroll_stages 156s ok 6 /driver/set_nr_enroll_stages 156s ok 7 /driver/supports_identify 156s ok 8 /driver/supports_capture 156s ok 9 /driver/has_storage 156s ok 10 /driver/do_not_support_identify 156s ok 11 /driver/do_not_support_capture 156s ok 12 /driver/has_not_storage 156s ok 13 /driver/get_usb_device 156s ok 14 /driver/get_virtual_env 156s ok 15 /driver/get_driver_data 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 156s # 156s # libfprint-device-DEBUG: Device reported probe completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 16 /driver/initial_features 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 156s # 156s # libfprint-device-DEBUG: Device reported probe completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 17 /driver/probe 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 18 /driver/open 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 19 /driver/close 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 156s # 156s # libfprint-device-DEBUG: Device reported enroll completion 156s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s ok 20 /driver/enroll 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 156s # 156s # libfprint-device-DEBUG: Device reported verify result 156s # libfprint-device-DEBUG: Device reported verify completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s ok 21 /driver/verify 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 156s # 156s # libfprint-device-DEBUG: Device reported identify result 156s # libfprint-device-DEBUG: Device reported identify completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s ok 22 /driver/identify 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 156s # 156s # libfprint-device-DEBUG: Device reported capture completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 156s ok 23 /driver/capture 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 156s # 156s # libfprint-device-DEBUG: Device reported listing completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 24 /driver/list 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 156s # 156s # libfprint-device-DEBUG: Device reported deletion completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 25 /driver/delete 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 156s # 156s # libfprint-device-DEBUG: Device reported deletion completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 156s # 156s # libfprint-device-DEBUG: Device reported close completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s ok 26 /driver/clear_storage 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 156s # 156s # libfprint-device-DEBUG: Device reported open completion 156s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 156s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 156s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 156s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 156s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 157s # 157s # libfprint-device-DEBUG: Device reported deletion completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 27 /driver/cancel 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 157s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 157s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 157s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 157s # 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 28 /driver/critical 157s ok 29 /driver/get_current_action 157s ok 30 /driver/timeout 157s ok 31 /driver/error_types 157s ok 32 /driver/retry_error_types 157s # Start of get_scan_type tests 157s ok 33 /driver/get_scan_type/press 157s ok 34 /driver/get_scan_type/swipe 157s # End of get_scan_type tests 157s # Start of set_scan_type tests 157s ok 35 /driver/set_scan_type/press 157s ok 36 /driver/set_scan_type/swipe 157s # End of set_scan_type tests 157s # Start of finger_status tests 157s ok 37 /driver/finger_status/inactive 157s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s ok 38 /driver/finger_status/waiting 157s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s ok 39 /driver/finger_status/present 157s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 157s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 157s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 157s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 157s ok 40 /driver/finger_status/changes 157s # End of finger_status tests 157s # Start of features tests 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 157s # 157s # libfprint-device-DEBUG: Device reported probe completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 41 /driver/features/probe_updates 157s # End of features tests 157s # Start of initial_features tests 157s ok 42 /driver/initial_features/none 157s ok 43 /driver/initial_features/no_capture 157s ok 44 /driver/initial_features/no_verify 157s ok 45 /driver/initial_features/no_identify 157s ok 46 /driver/initial_features/no_storage 157s ok 47 /driver/initial_features/no_list 157s ok 48 /driver/initial_features/no_delete 157s ok 49 /driver/initial_features/no_clear 157s # End of initial_features tests 157s # Start of probe tests 157s # libfprint-device-DEBUG: Device reported probe completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 50 /driver/probe/error 157s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 157s # libfprint-device-DEBUG: Device reported probe completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 51 /driver/probe/action_error 157s # End of probe tests 157s # Start of open tests 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 52 /driver/open/error 157s # End of open tests 157s # Start of close tests 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 53 /driver/close/error 157s # End of close tests 157s # Start of enroll tests 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 157s # 157s # libfprint-device-DEBUG: Device reported enroll completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 54 /driver/enroll/error 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported enroll progress, reported 735861869 of 248460373 have been completed 157s # libfprint-device-DEBUG: Device reported enroll progress, reported 2046909406 of 248460373 have been completed 157s # libfprint-device-DEBUG: Device reported enroll progress, reported 983876963 of 248460373 have been completed 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 157s # 157s # libfprint-device-DEBUG: Device reported enroll completion 157s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 55 /driver/enroll/progress 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 157s # 157s # libfprint-device-DEBUG: Device reported enroll completion 157s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 56 /driver/enroll/update_nbis 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 57 /driver/enroll/update_nbis_wrong_device 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 58 /driver/enroll/update_nbis_wrong_driver 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 59 /driver/enroll/update_nbis_missing_feature 157s # Start of error tests 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported enroll completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Device reported enroll completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Device reported enroll completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 60 /driver/enroll/error/no_print 157s # End of error tests 157s # End of enroll tests 157s # Start of verify tests 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 157s # 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 61 /driver/verify/fail 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 157s # 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 62 /driver/verify/retry 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 157s # 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 63 /driver/verify/error 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 64 /driver/verify/not_supported 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 65 /driver/verify/report_no_cb 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 66 /driver/verify/not_reported 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Device reported verify result 157s # libfprint-device-DEBUG: Device reported verify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 67 /driver/verify/complete_retry 157s # End of verify tests 157s # Start of identify tests 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 157s ok 68 /driver/identify/fail 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 157s ok 69 /driver/identify/retry 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 157s ok 70 /driver/identify/error 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 71 /driver/identify/not_reported 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 72 /driver/identify/complete_retry 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 73 /driver/identify/report_no_cb 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 74 /driver/identify/suspend_continues 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-device-DEBUG: Device reported identify result 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 157s ok 75 /driver/identify/suspend_succeeds 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 157s # 157s # libfprint-device-DEBUG: Device reported identify completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 157s ok 76 /driver/identify/suspend_busy_error 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 157s # 157s # libfprint-device-DEBUG: Device reported close completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s ok 77 /driver/identify/suspend_while_idle 157s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 157s # 157s # libfprint-device-DEBUG: Device reported open completion 157s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 157s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 159s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 159s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 159s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 159s # 159s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 159s # 159s # libfprint-device-DEBUG: Device reported identify completion 159s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 159s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 159s Executing: libfprint-2/fpi-device.test 161s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 164s Executing: libfprint-2/fpi-device.test 164s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 78 /driver/identify/warmup_cooldown 164s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 164s # End of identify tests 164s # Start of capture tests 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 79 /driver/capture/not_supported 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 164s # 164s # libfprint-device-DEBUG: Device reported capture completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s ok 80 /driver/capture/error 164s # End of capture tests 164s # Start of list tests 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 164s # 164s # libfprint-device-DEBUG: Device reported listing completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 81 /driver/list/error 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 82 /driver/list/no_storage 164s # End of list tests 164s # Start of delete tests 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 164s # 164s # libfprint-device-DEBUG: Device reported deletion completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 83 /driver/delete/error 164s # End of delete tests 164s # Start of clear_storage tests 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 164s # 164s # libfprint-device-DEBUG: Device reported deletion completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 84 /driver/clear_storage/error 164s # End of clear_storage tests 164s # Start of cancel tests 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 164s # 164s # libfprint-device-DEBUG: Device reported deletion completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 85 /driver/cancel/fail 164s # End of cancel tests 164s # Start of get_current_action tests 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 86 /driver/get_current_action/open 164s # End of get_current_action tests 164s # Start of get_cancellable tests 164s ok 87 /driver/get_cancellable/error 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 88 /driver/get_cancellable/open 164s # Start of open tests 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 89 /driver/get_cancellable/open/internal 164s # End of open tests 164s # End of get_cancellable tests 164s # Start of action_is_cancelled tests 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 90 /driver/action_is_cancelled/open 164s ok 91 /driver/action_is_cancelled/error 164s # Start of open tests 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 92 /driver/action_is_cancelled/open/internal 164s # End of open tests 164s # End of action_is_cancelled tests 164s # Start of complete_action tests 164s # Start of all tests 164s ok 93 /driver/complete_action/all/error 164s # End of all tests 164s # End of complete_action tests 164s # Start of action_error tests 164s ok 94 /driver/action_error/error 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 164s # libfprint-device-DEBUG: Device reported enroll completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 164s # libfprint-device-DEBUG: Device reported verify completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 164s # libfprint-device-DEBUG: Device reported identify completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 164s # libfprint-device-DEBUG: Device reported capture completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 164s # libfprint-device-DEBUG: Device reported listing completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 164s # libfprint-device-DEBUG: Device reported deletion completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 164s # libfprint-device-DEBUG: Device reported deletion completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s ok 95 /driver/action_error/all 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 164s # 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 164s # 164s # libfprint-device-DEBUG: Device reported enroll completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 164s # 164s # libfprint-device-DEBUG: Device reported verify completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 164s # 164s # libfprint-device-DEBUG: Device reported identify completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 164s # 164s # libfprint-device-DEBUG: Device reported capture completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 164s # 164s # libfprint-device-DEBUG: Device reported listing completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 164s # 164s # libfprint-device-DEBUG: Device reported deletion completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 164s # 164s # libfprint-device-DEBUG: Device reported deletion completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 164s # 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s ok 96 /driver/action_error/fail 164s # End of action_error tests 164s # Start of timeout tests 164s ok 97 /driver/timeout/cancelled 164s # End of timeout tests 164s # End of driver tests 164s PASS: libfprint-2/fpi-device.test 164s Running test: libfprint-2/driver-egismoc-0587.test 164s ** (umockdev-run:4069): DEBUG: 20:26:12.436: umockdev.vala:127: Created udev test bed /tmp/umockdev.LSM812 164s ** (umockdev-run:4069): DEBUG: 20:26:12.436: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 164s ** (umockdev-run:4069): DEBUG: 20:26:12.437: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 164s ** (umockdev-run:4069): DEBUG: 20:26:12.441: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.LSM812/dev/bus/usb/003/009 164s ** (umockdev-run:4069): DEBUG: 20:26:12.441: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 164s ** (umockdev-run:4069): DEBUG: 20:26:12.442: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 164s ** (umockdev-run:4069): DEBUG: 20:26:12.445: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.LSM812/dev/bus/usb/003/001 164s ** (umockdev-run:4069): DEBUG: 20:26:12.445: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 164s ** (umockdev-run:4069): DEBUG: 20:26:12.446: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 164s (process:4073): libfprint-context-DEBUG: 20:26:12.525: Initializing FpContext (libfprint version 1.94.8+tod1) 164s (process:4073): libfprint-tod-DEBUG: 20:26:12.525: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.527: 132323058: ../libfprint/drivers/egismoc/egismoc.c:1597 164s (process:4073): libfprint-context-DEBUG: 20:26:12.527: No driver found for USB device 1D6B:0002 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.527: egismoc_probe enter --> 164s (process:4073): libfprint-device-DEBUG: 20:26:12.529: Device reported probe completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.529: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.529: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.529: Opening device 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.530: [egismoc] DEV_INIT_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.530: [egismoc] DEV_INIT_STATES entering state 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.531: [egismoc] DEV_INIT_STATES entering state 2 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.531: [egismoc] DEV_INIT_STATES entering state 3 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.532: [egismoc] DEV_INIT_STATES entering state 4 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.532: [egismoc] DEV_INIT_STATES entering state 5 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.532: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.532: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.532: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.532: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.533: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: Firmware version callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: Device firmware version is 9050.6.4.67 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.533: [egismoc] DEV_INIT_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.533: Device reported open completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.533: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.533: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: List 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.533: [egismoc] LIST_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.533: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.533: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.534: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.534: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.534: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.534: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.534: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.534: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.534: [egismoc] LIST_STATES entering state 1 164s (process:4073): libfprint-device-DEBUG: 20:26:12.534: Device reported listing completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.534: [egismoc] LIST_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.534: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.534: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.535: Clear storage 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.535: [egismoc] DELETE_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.535: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.535: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.535: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.535: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.536: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.536: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.536: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.536: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.536: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.536: [egismoc] DELETE_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.536: Get delete command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.536: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.536: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.536: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.536: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.537: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.537: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.537: Delete callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.537: Response prefix valid: yes 164s (process:4073): libfprint-device-DEBUG: 20:26:12.537: Device reported deletion completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.537: [egismoc] DELETE_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.537: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.537: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.537: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.537: List 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.537: [egismoc] LIST_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.537: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.537: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.537: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.537: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.538: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.538: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.538: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.538: Number of currently enrolled fingerprints on the device is 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.538: [egismoc] LIST_STATES entering state 1 164s (process:4073): libfprint-device-DEBUG: 20:26:12.538: Device reported listing completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.538: [egismoc] LIST_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.538: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.538: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.538: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:4073): libfprint-device-DEBUG: 20:26:12.538: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.538: Enroll 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.538: [egismoc] ENROLL_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.538: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.538: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.538: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.538: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.539: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.539: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.539: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.539: Number of currently enrolled fingerprints on the device is 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.539: [egismoc] ENROLL_STATES entering state 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.539: [egismoc] ENROLL_STATES entering state 2 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.539: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.539: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.539: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.540: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.540: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.540: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.540: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.540: [egismoc] ENROLL_STATES entering state 3 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.540: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.540: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.540: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.540: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.541: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.541: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.541: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.541: [egismoc] ENROLL_STATES entering state 4 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.541: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.541: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.541: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.541: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.541: [egismoc] ENROLL_STATES entering state 5 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.541: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.541: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.541: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.542: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.542: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.542: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.542: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.542: [egismoc] ENROLL_STATES entering state 6 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.542: Get check command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.542: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.542: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.542: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.543: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.543: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.543: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.543: Enroll check callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.543: Response suffix valid: yes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.543: [egismoc] ENROLL_STATES entering state 7 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.543: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.543: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.543: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.544: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.544: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.544: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.544: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.544: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.544: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.544: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.544: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.545: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.545: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.545: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.545: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.545: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.545: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.545: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.545: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.546: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.546: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.546: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.546: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.546: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.546: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.546: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.547: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.547: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.547: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.547: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.547: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.547: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.547: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.548: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.548: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.548: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.548: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.548: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.548: Partial capture successful. Please touch the sensor again (1/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.548: Device reported enroll progress, reported 1 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.548: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.548: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.548: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.548: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.548: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.549: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.549: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.549: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.549: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.549: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.549: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.549: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.549: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.550: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.550: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.550: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.550: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.550: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.550: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.550: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.550: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.550: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.550: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.550: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.550: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.551: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.551: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.551: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.551: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.551: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.551: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.551: Partial capture successful. Please touch the sensor again (2/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.551: Device reported enroll progress, reported 2 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.551: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.551: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.551: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.551: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.552: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.552: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.552: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.552: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.552: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.552: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.552: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.552: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.553: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.554: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.554: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.554: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.554: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.554: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.554: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.554: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.554: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.554: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.554: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.554: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.554: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.554: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.555: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.555: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.555: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.555: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.555: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.555: Partial capture successful. Please touch the sensor again (3/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.555: Device reported enroll progress, reported 3 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.555: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.555: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.555: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.555: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.555: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.556: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.556: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.556: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.556: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.556: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.556: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.556: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.557: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.557: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.557: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.557: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.557: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.557: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.557: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.558: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.558: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.558: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.558: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.558: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.558: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.558: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.559: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Partial capture successful. Please touch the sensor again (4/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.559: Device reported enroll progress, reported 4 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.559: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.559: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.559: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.559: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.559: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.559: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.560: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.560: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.560: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.560: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.560: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.560: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.560: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.560: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.561: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.561: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.561: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.561: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.561: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.561: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.561: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.562: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.562: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.562: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.562: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.562: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.562: Partial capture successful. Please touch the sensor again (5/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.562: Device reported enroll progress, reported 5 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.562: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.562: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.562: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.562: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.562: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.563: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.563: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.563: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.563: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.563: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.563: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.563: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.563: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.564: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.564: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.564: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.564: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.564: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.564: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.564: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.564: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.564: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.564: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.564: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.564: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.565: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.565: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.565: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.565: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.565: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.565: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.565: Partial capture successful. Please touch the sensor again (6/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.565: Device reported enroll progress, reported 6 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.565: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.565: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.565: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.565: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.566: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.566: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.566: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.566: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.566: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.566: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.566: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.566: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.566: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.567: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.567: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.567: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.567: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.567: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.567: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.567: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.567: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.567: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.567: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.567: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.567: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.568: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.568: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.568: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.568: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.568: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.568: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.568: Partial capture successful. Please touch the sensor again (7/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.568: Device reported enroll progress, reported 7 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.568: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.568: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.568: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.568: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.569: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.569: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.569: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.569: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.569: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.569: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.569: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.569: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.570: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.570: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.570: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.570: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.570: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.570: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.570: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.571: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.571: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.571: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.571: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.571: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.571: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.571: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.572: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.572: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.572: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.572: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.572: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.572: Partial capture successful. Please touch the sensor again (8/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.572: Device reported enroll progress, reported 8 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.572: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.572: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.572: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.572: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.572: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.573: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.573: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.573: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.573: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.573: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.573: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.573: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.574: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.575: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.575: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.575: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.575: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.575: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.575: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.575: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.575: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.575: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.575: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.575: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.575: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.576: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.576: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.576: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.576: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.576: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.576: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.576: Partial capture successful. Please touch the sensor again (9/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.576: Device reported enroll progress, reported 9 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.577: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.577: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.577: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.577: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.577: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.577: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.577: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.577: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.577: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.577: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.577: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.577: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.578: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.578: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.578: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.578: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.578: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.578: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.578: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.579: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.579: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.579: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.579: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.579: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.579: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.579: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.580: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Response suffix valid: NO 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Response suffix valid: yes 164s (process:4073): libfprint-device-DEBUG: 20:26:12.580: Device reported enroll progress, reported 9 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.580: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.580: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.580: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.580: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.581: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.581: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.581: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.581: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.581: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.581: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.581: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.581: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.581: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.581: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.581: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.581: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.581: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.582: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.582: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.582: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.582: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.582: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.582: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.582: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.583: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.583: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.583: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.583: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.583: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.583: Partial capture successful. Please touch the sensor again (10/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.583: Device reported enroll progress, reported 10 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.583: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.583: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.583: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.583: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.583: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.584: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.584: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.584: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.584: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.584: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.584: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.584: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.584: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.585: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.585: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.585: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.585: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.585: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.585: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.585: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.585: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.585: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.585: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.585: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.586: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.586: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Response suffix valid: NO 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Response suffix valid: yes 164s (process:4073): libfprint-device-DEBUG: 20:26:12.586: Device reported enroll progress, reported 10 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.586: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.586: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.586: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.586: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.587: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.587: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.587: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.587: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.587: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.587: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.587: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.587: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.588: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.588: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.588: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.588: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.588: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.588: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.588: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.588: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.588: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.588: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.588: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.588: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.589: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.589: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.589: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.589: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.589: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.589: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.589: Partial capture successful. Please touch the sensor again (11/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.589: Device reported enroll progress, reported 11 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.589: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.589: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.589: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.589: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.589: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.590: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.590: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.590: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.590: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.590: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.590: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.590: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.590: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.590: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.590: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.590: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.590: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.590: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.590: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.591: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.591: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.591: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.591: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.591: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.591: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.591: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.592: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Partial capture successful. Please touch the sensor again (12/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.592: Device reported enroll progress, reported 12 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.592: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.592: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.592: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.592: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.592: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.592: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.592: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.593: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.593: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.593: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.593: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.593: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.593: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.593: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.594: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.594: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.594: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.594: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.594: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Partial capture successful. Please touch the sensor again (13/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.594: Device reported enroll progress, reported 13 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.594: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.594: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.594: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.595: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.595: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.595: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.595: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.595: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.595: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.595: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.595: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.596: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.596: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.596: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.596: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.596: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.596: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.596: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.596: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.596: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.596: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.596: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.596: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.596: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.597: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.597: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.597: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.597: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.597: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.597: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.597: Partial capture successful. Please touch the sensor again (14/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.597: Device reported enroll progress, reported 14 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.597: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.597: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.597: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.597: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.598: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.598: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.598: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.598: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.598: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.598: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.598: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.598: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.599: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.599: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.599: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.599: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.599: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.599: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.599: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.599: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.599: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.599: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.599: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.599: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.599: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.600: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.600: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.600: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.600: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.600: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.600: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.600: Partial capture successful. Please touch the sensor again (15/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.600: Device reported enroll progress, reported 15 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.600: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.600: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.600: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.600: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.601: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.601: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.601: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.601: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.601: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.601: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.601: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.601: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.601: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.602: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.602: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.602: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.602: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.602: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.602: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.602: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.602: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.602: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.602: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.602: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.602: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.603: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.603: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.603: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.603: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.603: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.603: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.603: Partial capture successful. Please touch the sensor again (16/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.603: Device reported enroll progress, reported 16 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.603: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.603: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.603: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.603: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.604: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.604: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.604: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.604: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.604: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.604: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.604: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.604: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.605: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.605: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.605: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.605: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.605: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.605: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.605: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.606: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.606: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.606: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.606: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.606: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Partial capture successful. Please touch the sensor again (17/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.606: Device reported enroll progress, reported 17 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.606: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.606: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.606: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.607: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.607: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.607: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.607: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.607: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.607: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.607: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.607: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.608: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.608: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.608: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.608: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.608: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.608: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.608: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.609: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.609: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.609: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.609: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.609: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Partial capture successful. Please touch the sensor again (18/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.609: Device reported enroll progress, reported 18 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.609: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.609: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.609: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.610: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.610: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.610: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.610: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.610: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.610: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.610: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.610: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.611: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.611: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.611: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.611: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.611: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.611: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.611: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.611: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.611: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.611: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.611: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.611: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.611: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.612: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.612: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.612: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.612: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.612: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.612: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.612: Partial capture successful. Please touch the sensor again (19/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.612: Device reported enroll progress, reported 19 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.612: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.612: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.612: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.612: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.613: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.613: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.613: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.613: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.613: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.613: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.613: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.613: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.613: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.614: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.614: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.614: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.614: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.614: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.614: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.614: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.614: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.614: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.614: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.614: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.614: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.615: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.615: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.615: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.615: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.615: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.615: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.615: Partial capture successful. Please touch the sensor again (20/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.615: Device reported enroll progress, reported 20 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.615: [egismoc] ENROLL_STATES entering state 12 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.615: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.615: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.615: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.615: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.616: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.616: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.616: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.616: [egismoc] ENROLL_STATES entering state 13 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.616: New fingerprint ID: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.616: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.616: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.616: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.616: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.617: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.617: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.617: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.617: [egismoc] ENROLL_STATES entering state 14 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.617: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.617: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.617: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.617: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.617: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.617: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.617: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.617: [egismoc] ENROLL_STATES entering state 15 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.617: Enrollment was successful! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.617: Device reported enroll completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.617: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4073): libfprint-device-DEBUG: 20:26:12.618: Print for finger FP_FINGER_LEFT_INDEX enrolled 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.618: [egismoc] ENROLL_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.618: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.618: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.618: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.618: List 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.618: [egismoc] LIST_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.618: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.618: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.618: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.618: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.618: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.619: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.619: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.619: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.619: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.619: [egismoc] LIST_STATES entering state 1 164s (process:4073): libfprint-device-DEBUG: 20:26:12.619: Device reported listing completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.619: [egismoc] LIST_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.619: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.619: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.619: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-device-DEBUG: 20:26:12.619: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.619: Identify or Verify 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.619: [egismoc] IDENTIFY_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.619: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.619: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.619: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.620: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.620: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.620: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.620: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.620: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.620: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.620: [egismoc] IDENTIFY_STATES entering state 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.620: [egismoc] IDENTIFY_STATES entering state 2 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.620: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.620: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.620: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.621: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.621: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.621: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.621: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.621: [egismoc] IDENTIFY_STATES entering state 3 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.621: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.621: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.621: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.622: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.622: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.622: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.622: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.622: [egismoc] IDENTIFY_STATES entering state 4 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.622: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.622: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.623: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.623: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.623: [egismoc] IDENTIFY_STATES entering state 5 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.623: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.623: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.623: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.623: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.624: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.624: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.624: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.624: [egismoc] IDENTIFY_STATES entering state 6 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.624: Get check command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.624: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.624: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.624: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.624: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.625: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.625: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.625: Identify check callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.625: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.625: Identify successful for: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.625: Verifying against: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-device-DEBUG: 20:26:12.625: Device reported verify result 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.625: [egismoc] IDENTIFY_STATES entering state 7 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.625: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.625: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.625: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.625: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.626: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.626: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.626: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.626: [egismoc] IDENTIFY_STATES entering state 8 164s (process:4073): libfprint-device-DEBUG: 20:26:12.626: Device reported verify completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.626: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.626: [egismoc] IDENTIFY_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.626: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.626: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.626: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-device-DEBUG: 20:26:12.626: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.626: Identify or Verify 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.626: [egismoc] IDENTIFY_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.626: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.626: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.626: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.627: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.627: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.627: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.628: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.628: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.628: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.628: [egismoc] IDENTIFY_STATES entering state 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.628: [egismoc] IDENTIFY_STATES entering state 2 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.628: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.628: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.628: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.628: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.629: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.629: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.629: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.629: [egismoc] IDENTIFY_STATES entering state 3 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.629: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.629: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.629: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.630: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.630: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.630: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.630: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.630: [egismoc] IDENTIFY_STATES entering state 4 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.630: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.631: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.631: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.631: [egismoc] IDENTIFY_STATES entering state 5 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.631: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.631: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.631: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.631: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.632: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.632: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.632: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.632: [egismoc] IDENTIFY_STATES entering state 6 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.632: Get check command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.632: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.632: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.632: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.632: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.633: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.633: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.633: Identify check callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.633: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.633: Identify successful for: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-device-DEBUG: 20:26:12.633: Device reported identify result 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.633: [egismoc] IDENTIFY_STATES entering state 7 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.633: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.633: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.633: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.633: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.634: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.634: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.634: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.634: [egismoc] IDENTIFY_STATES entering state 8 164s (process:4073): libfprint-device-DEBUG: 20:26:12.634: Device reported identify completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.634: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.634: [egismoc] IDENTIFY_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.634: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.634: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.634: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-device-DEBUG: 20:26:12.635: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.635: Enroll 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.635: [egismoc] ENROLL_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.635: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.635: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.635: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.635: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.635: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.636: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.636: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.636: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.636: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.636: [egismoc] ENROLL_STATES entering state 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.636: [egismoc] ENROLL_STATES entering state 2 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.636: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.636: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.636: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.636: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.637: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.637: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.637: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.637: [egismoc] ENROLL_STATES entering state 3 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.637: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.637: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.637: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.637: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.638: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.638: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.638: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.638: [egismoc] ENROLL_STATES entering state 4 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.638: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.638: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.638: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.638: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.638: [egismoc] ENROLL_STATES entering state 5 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.638: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.639: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.639: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.639: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.639: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.639: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.639: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.639: [egismoc] ENROLL_STATES entering state 6 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.639: Get check command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.639: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.639: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.640: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.640: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.641: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.641: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.641: Enroll check callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.641: Response suffix valid: NO 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.641: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.641: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.641: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.641: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 164s (process:4073): libfprint-device-DEBUG: 20:26:12.641: Device reported enroll completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.641: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4073): libfprint-device-DEBUG: 20:26:12.641: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.641: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.641: List 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.641: [egismoc] LIST_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.641: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.641: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.641: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.641: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.642: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.642: [egismoc] LIST_STATES entering state 1 164s (process:4073): libfprint-device-DEBUG: 20:26:12.642: Device reported listing completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.642: [egismoc] LIST_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.642: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.642: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-device-DEBUG: 20:26:12.642: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: Enroll 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.642: [egismoc] ENROLL_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.642: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.642: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.643: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.643: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.643: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.643: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.643: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.643: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.643: [egismoc] ENROLL_STATES entering state 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.643: [egismoc] ENROLL_STATES entering state 2 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.643: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.643: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.643: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.644: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.644: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.644: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.644: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.644: [egismoc] ENROLL_STATES entering state 3 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.644: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.644: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.644: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.645: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.645: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.645: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.645: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.645: [egismoc] ENROLL_STATES entering state 4 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.645: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.645: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.646: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.646: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.646: [egismoc] ENROLL_STATES entering state 5 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.646: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.646: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.646: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.646: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.647: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.647: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.647: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.647: [egismoc] ENROLL_STATES entering state 6 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.647: Get check command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.647: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.647: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.647: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.647: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.648: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.648: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.648: Enroll check callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.648: Response suffix valid: yes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.648: [egismoc] ENROLL_STATES entering state 7 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.648: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.648: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.648: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.648: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.649: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.649: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.649: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.649: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.649: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.649: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.649: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.649: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.650: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.650: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.650: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.650: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.650: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.650: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.650: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.650: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.651: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.651: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.651: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.651: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.651: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.651: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.651: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.651: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.651: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.651: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.651: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.651: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.652: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.652: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.652: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.652: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.652: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.652: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.652: Partial capture successful. Please touch the sensor again (1/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.652: Device reported enroll progress, reported 1 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.652: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.652: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.652: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.652: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.653: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.653: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.653: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.653: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.653: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.653: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.653: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.653: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.654: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.654: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.654: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.654: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.654: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.654: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.654: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.654: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.654: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.654: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.654: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.654: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.654: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.655: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.655: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.655: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.655: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.655: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.655: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.655: Partial capture successful. Please touch the sensor again (2/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.655: Device reported enroll progress, reported 2 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.655: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.655: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.655: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.655: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.656: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.656: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.656: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.656: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.656: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.656: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.656: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.656: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.657: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.657: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.657: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.657: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.657: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.657: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.658: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.658: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.658: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.658: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.658: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.658: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.658: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.659: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.659: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.659: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.659: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.659: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.659: Partial capture successful. Please touch the sensor again (3/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.659: Device reported enroll progress, reported 3 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.659: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.659: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.659: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.659: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.659: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.660: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.660: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.660: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.660: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.660: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.660: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.660: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.660: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.661: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.661: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.661: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.661: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.661: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.661: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.661: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.661: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.661: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.661: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.661: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.661: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.662: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.662: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.662: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.662: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.662: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.662: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.662: Partial capture successful. Please touch the sensor again (4/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.662: Device reported enroll progress, reported 4 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.662: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.662: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.662: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.662: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.663: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.663: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.663: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.663: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.663: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.663: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.663: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.663: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.664: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.664: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.664: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.664: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.664: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.664: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.664: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.664: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.664: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.664: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.664: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.664: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.665: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.665: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.665: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.665: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.665: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.665: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.665: Partial capture successful. Please touch the sensor again (5/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.665: Device reported enroll progress, reported 5 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.665: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.665: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.665: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.665: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.666: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.666: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.666: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.666: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.666: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.666: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.666: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.666: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.667: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.667: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.667: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.667: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.667: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.667: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.667: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.668: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.668: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.668: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.668: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.668: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.668: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.668: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.669: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.669: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.669: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.669: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.669: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.669: Partial capture successful. Please touch the sensor again (6/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.669: Device reported enroll progress, reported 6 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.669: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.669: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.669: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.669: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.669: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.670: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.670: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.670: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.670: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.670: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.670: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.670: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.670: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.671: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.671: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.671: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.671: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.671: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.671: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.671: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.671: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.671: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.671: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.671: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.671: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.672: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.672: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.672: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.672: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.672: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.672: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.672: Partial capture successful. Please touch the sensor again (7/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.672: Device reported enroll progress, reported 7 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.672: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.672: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.672: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.672: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.673: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.673: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.673: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.673: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.673: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.673: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.673: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.673: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.674: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.674: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.674: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.674: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.674: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.674: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.674: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.675: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.675: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.675: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.675: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.675: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.675: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.675: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.676: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Response suffix valid: NO 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Response suffix valid: yes 164s (process:4073): libfprint-device-DEBUG: 20:26:12.676: Device reported enroll progress, reported 7 of 20 have been completed 164s listing - device should have prints 164s clear device storage 164s clear done 164s listing - device should be empty 164s enrolling 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 1, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 2, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 3, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 4, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 5, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 6, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 7, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 8, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 9, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 10, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 11, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 12, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 13, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 14, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 15, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 16, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 17, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 18, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 19, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 20, , None, None) 164s enroll done 164s listing - device should have 1 print 164s verifying 164s verify done 164s async identifying 164s indentification_done: 164s try to enroll duplicate 164s duplicate enroll attempt done 164s listing - device should still only have 1 print 164s enroll new finger 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 1, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 2, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 3, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 4, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 5, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 6, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 7, , None, None) 164s finger status: (process:4073): libfprint-SSM-DEBUG: 20:26:12.676: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.676: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.676: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.676: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.677: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.677: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.677: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.677: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.677: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.677: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.677: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.677: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.678: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.678: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.678: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.678: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.678: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.678: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.678: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.678: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.678: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.678: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.678: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.678: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.679: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.679: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.679: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.679: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.679: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.679: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.679: Partial capture successful. Please touch the sensor again (8/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.679: Device reported enroll progress, reported 8 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.679: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.679: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.679: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.679: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.680: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.680: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.680: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.680: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.680: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.680: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.680: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.680: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.681: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.681: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.681: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.681: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.681: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.681: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.682: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.682: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.682: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.682: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.682: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.682: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.682: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.683: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Response suffix valid: NO 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Response suffix valid: yes 164s (process:4073): libfprint-device-DEBUG: 20:26:12.683: Device reported enroll progress, reported 8 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.683: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.683: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.683: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.683: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.684: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.684: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.684: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.684: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.684: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.684: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.684: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.684: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.685: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.685: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.685: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.685: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.685: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.685: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.685: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.685: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.685: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.685: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.685: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.685: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.685: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.686: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.686: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.686: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.686: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.686: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.686: Partial capture successful. Please touch the sensor again (9/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.686: Device reported enroll progress, reported 9 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.686: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.686: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.686: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.686: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.686: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.687: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.687: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.687: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.687: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.687: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.687: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.687: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.687: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.688: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.688: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.688: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.688: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.688: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.688: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.688: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.688: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.688: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.688: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.688: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.689: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.689: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.689: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.689: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.689: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.689: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.689: Partial capture successful. Please touch the sensor again (10/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.689: Device reported enroll progress, reported 10 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.689: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.689: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.689: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.689: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.690: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.690: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.690: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.690: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.690: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.690: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.690: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.690: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.691: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.691: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.691: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.691: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.691: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.691: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.692: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.692: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.692: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.692: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.692: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.692: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.692: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.693: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.693: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.693: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.693: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.693: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.693: Partial capture successful. Please touch the sensor again (11/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.693: Device reported enroll progress, reported 11 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.693: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.693: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.693: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.693: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.693: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.694: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.694: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.694: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.694: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.694: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.694: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.694: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.694: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.695: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.695: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.695: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.695: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.695: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.695: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.695: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.695: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.695: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.695: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.695: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.695: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.696: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.696: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.696: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.696: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.696: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.696: Partial capture successful. Please touch the sensor again (12/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.696: Device reported enroll progress, reported 12 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.696: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.696: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.696: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.696: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.696: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.697: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.697: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.697: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.697: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.697: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.697: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.697: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.697: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.698: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.698: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.698: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.698: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.698: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.698: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.698: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.698: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.698: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.698: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.698: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.698: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.698: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.699: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.699: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.699: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.699: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.699: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.699: Partial capture successful. Please touch the sensor again (13/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.699: Device reported enroll progress, reported 13 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.699: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.699: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.699: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.699: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.699: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.700: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.700: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.700: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.700: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.700: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.700: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.700: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.700: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.701: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.701: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.701: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.701: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.701: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.701: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.701: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.701: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.701: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.701: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.701: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.702: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.702: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.702: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.702: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.702: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.702: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.702: Partial capture successful. Please touch the sensor again (14/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.702: Device reported enroll progress, reported 14 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.702: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.702: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.702: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.702: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.703: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.703: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.703: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.703: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.703: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.703: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.703: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.703: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.703: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.704: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.704: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.704: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.704: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.704: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.704: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.705: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.705: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.705: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.705: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.705: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Partial capture successful. Please touch the sensor again (15/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.705: Device reported enroll progress, reported 15 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.705: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.705: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.705: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.706: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.706: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.706: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.706: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.706: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.706: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.706: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.706: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.707: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.707: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.707: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.707: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.707: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.707: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.707: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.708: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.708: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.708: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.708: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.708: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.708: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.708: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.709: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Partial capture successful. Please touch the sensor again (16/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.709: Device reported enroll progress, reported 16 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.709: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.709: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.709: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.709: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.709: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.709: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.709: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.710: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.710: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.710: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.710: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.710: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.710: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.710: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.711: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.711: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.711: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.711: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.711: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.711: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.711: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.712: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Partial capture successful. Please touch the sensor again (17/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.712: Device reported enroll progress, reported 17 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.712: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.712: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.712: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.712: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.713: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.713: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.713: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.713: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.713: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.713: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.713: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.713: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.713: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.713: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.713: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.713: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.714: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.714: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.714: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.714: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.714: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.714: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.714: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.715: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.715: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.715: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.715: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.715: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.715: Partial capture successful. Please touch the sensor again (18/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.715: Device reported enroll progress, reported 18 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.715: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.715: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.715: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.715: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.715: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.716: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.716: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.716: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.716: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.716: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.716: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.716: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.716: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.717: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.717: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.717: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.717: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.717: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.717: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.717: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.717: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.717: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.717: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.717: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.717: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.717: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.718: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.718: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.718: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.718: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.718: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.718: Partial capture successful. Please touch the sensor again (19/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.718: Device reported enroll progress, reported 19 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.718: [egismoc] ENROLL_STATES entering state 8 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.718: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.718: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.718: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.718: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.719: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.719: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.719: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.719: [egismoc] ENROLL_STATES entering state 9 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.719: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.719: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.719: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.719: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.720: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.720: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.720: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.720: [egismoc] ENROLL_STATES entering state 10 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.720: Wait for finger on sensor 164s (process:4073): libfprint-device-DEBUG: 20:26:12.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.720: Finger on sensor callback 164s (process:4073): libfprint-device-DEBUG: 20:26:12.720: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.720: [egismoc] ENROLL_STATES entering state 11 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.720: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.720: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.720: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.721: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.721: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.721: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.721: Read capture callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.721: Response prefix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.721: Response suffix valid: yes 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.721: Partial capture successful. Please touch the sensor again (20/20) 164s (process:4073): libfprint-device-DEBUG: 20:26:12.721: Device reported enroll progress, reported 20 of 20 have been completed 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.721: [egismoc] ENROLL_STATES entering state 12 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.721: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.721: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.721: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.721: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.722: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.722: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.722: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.722: [egismoc] ENROLL_STATES entering state 13 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.722: New fingerprint ID: FP1-00000000-7-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.722: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.722: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.722: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.722: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.723: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.723: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.723: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.723: [egismoc] ENROLL_STATES entering state 14 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.723: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.723: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.723: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.723: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.724: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.724: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.724: Task SSM next state callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.724: [egismoc] ENROLL_STATES entering state 15 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.724: Enrollment was successful! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.724: Device reported enroll completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.724: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4073): libfprint-device-DEBUG: 20:26:12.724: Print for finger FP_FINGER_RIGHT_INDEX enrolled 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.724: [egismoc] ENROLL_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.724: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.724: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.724: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.724: List 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.724: [egismoc] LIST_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.724: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.724: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.724: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.724: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.725: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Device fingerprint 2: FP1-00000000-7-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Number of currently enrolled fingerprints on the device is 2 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.725: [egismoc] LIST_STATES entering state 1 164s (process:4073): libfprint-device-DEBUG: 20:26:12.725: Device reported listing completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.725: [egismoc] LIST_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.725: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.725: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Delete 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.725: [egismoc] DELETE_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.725: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.725: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.725: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.726: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Device fingerprint 1: FP1-00000000-2-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Device fingerprint 2: FP1-00000000-7-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Number of currently enrolled fingerprints on the device is 2 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.726: [egismoc] DELETE_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Get delete command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.726: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.726: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.726: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.727: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.727: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.727: Delete callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.727: Response prefix valid: yes 164s (process:4073): libfprint-device-DEBUG: 20:26:12.727: Device reported deletion completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.727: [egismoc] DELETE_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.727: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.727: Completing action FPI_DEVICE_ACTION_DELETE in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.727: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.727: List 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.727: [egismoc] LIST_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.727: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.727: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.727: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.727: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.728: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: Device fingerprint 1: FP1-00000000-7-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.728: [egismoc] LIST_STATES entering state 1 164s (process:4073): libfprint-device-DEBUG: 20:26:12.728: Device reported listing completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.728: [egismoc] LIST_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.728: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.728: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: Clear storage 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.728: [egismoc] DELETE_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.728: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.728: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.728: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.729: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.729: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.729: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.729: Device fingerprint 1: FP1-00000000-7-00000000-nobody 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.729: Number of currently enrolled fingerprints on the device is 1 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.729: [egismoc] DELETE_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.729: Get delete command 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.729: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.729: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.729: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.729: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.730: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.730: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.730: Delete callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.730: Response prefix valid: yes 164s (process:4073): libfprint-device-DEBUG: 20:26:12.730: Device reported deletion completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.730: [egismoc] DELETE_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.730: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.730: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.730: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.730: List 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.730: [egismoc] LIST_STATES entering state 0 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.730: Execute command and get response 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.730: Get check bytes 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.730: [egismoc] CMD_STATES entering state 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.730: [egismoc] CMD_STATES entering state 1 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.731: Command receive callback 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.731: [egismoc] CMD_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.731: List callback 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.731: Number of currently enrolled fingerprints on the device is 0 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.731: [egismoc] LIST_STATES entering state 1 164s (process:4073): libfprint-device-DEBUG: 20:26:12.731: Device reported listing completion 164s (process:4073): libfprint-SSM-DEBUG: 20:26:12.731: [egismoc] LIST_STATES completed successfully 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.731: Task SSM done 164s (process:4073): libfprint-device-DEBUG: 20:26:12.731: Completing action FPI_DEVICE_ACTION_LIST in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.731: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.731: Closing device 164s (process:4073): libfprint-egismoc-DEBUG: 20:26:12.731: Cancel 164s (process:4073): libfprint-device-DEBUG: 20:26:12.731: Device reported close completion 164s (process:4073): libfprint-device-DEBUG: 20:26:12.731: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s (process:4073): libfprint-device-DEBUG: 20:26:12.731: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 164s 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 8, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 9, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 10, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 11, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 12, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 13, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 14, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 15, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 16, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 17, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 18, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 19, , None, None) 164s finger status: 164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x79db1a5da280 (FpiDeviceEgisMoc at 0x63f8950)>, 20, , None, None) 164s enroll new finger done 164s listing - device should have 2 prints 164s deleting first print 164s delete done 164s listing - device should only have second print 164s clear device storage 164s clear done 164s listing - device should be empty 164s ** (umockdev-run:4069): DEBUG: 20:26:12.746: umockdev.vala:154: Removing test bed /tmp/umockdev.LSM812 164s (umockdev-run:4069): GLib-DEBUG: 20:26:12.752: unsetenv() is not thread-safe and should not be used after threads are created 164s PASS: libfprint-2/driver-egismoc-0587.test 164s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.5.test 164s TAP version 14 164s # random seed: R02S07d60617fd35056a3b2f847e8102a426 164s 1..14 164s # Start of device tests 164s # Start of async tests 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.5 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.5 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 1 /device/async/open 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 2 /device/async/close 164s # End of async tests 164s # Start of sync tests 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 3 /device/sync/open 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 4 /device/sync/close 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 5 /device/sync/get_driver 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 6 /device/sync/get_device_id 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 7 /device/sync/get_name 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 8 /device/sync/get_scan_type 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 9 /device/sync/get_nr_enroll_stages 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 10 /device/sync/supports_identify 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 11 /device/sync/supports_capture 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 12 /device/sync/has_storage 164s # Start of open tests 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 13 /device/sync/open/notify 164s # End of open tests 164s # Start of close tests 164s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea018953b, GType is 101056592062752 164s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 164s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 164s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b7ea0174987, GType is 101056592067552 164s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 164s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 164s # libfprint-context-DEBUG: created 164s # libfprint-device-DEBUG: Device reported probe completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported open completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s # libfprint-device-DEBUG: Device reported close completion 164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 164s ok 14 /device/sync/close/notify 164s # End of close tests 164s # End of sync tests 164s # End of device tests 164s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.5.test 164s Running test: libfprint-2/driver-realtek-5816.test 164s ** (umockdev-run:4113): DEBUG: 20:26:12.816: umockdev.vala:127: Created udev test bed /tmp/umockdev.IRAH22 164s ** (umockdev-run:4113): DEBUG: 20:26:12.816: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6 164s ** (umockdev-run:4113): DEBUG: 20:26:12.817: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb) 164s ** (umockdev-run:4113): DEBUG: 20:26:12.821: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IRAH22/dev/bus/usb/001/006 164s ** (umockdev-run:4113): DEBUG: 20:26:12.821: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 164s ** (umockdev-run:4113): DEBUG: 20:26:12.822: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 164s ** (umockdev-run:4113): DEBUG: 20:26:12.825: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IRAH22/dev/bus/usb/001/001 164s ** (umockdev-run:4113): DEBUG: 20:26:12.825: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 164s ** (umockdev-run:4113): DEBUG: 20:26:12.825: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 164s (process:4117): libfprint-context-DEBUG: 20:26:12.900: Initializing FpContext (libfprint version 1.94.8+tod1) 164s (process:4117): libfprint-tod-DEBUG: 20:26:12.900: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 164s (process:4117): libfprint-context-DEBUG: 20:26:12.902: No driver found for USB device 1D6B:0002 164s (process:4117): libfprint-realtek-DEBUG: 20:26:12.902: 132698508: ../libfprint/drivers/realtek/realtek.c:1225 164s (process:4117): libfprint-realtek-DEBUG: 20:26:12.905: Device name: Realtek USB2.0 Finger Print Bridge 164s (process:4117): libfprint-device-DEBUG: 20:26:12.905: Device reported probe completion 164s (process:4117): libfprint-device-DEBUG: 20:26:12.905: Completing action FPI_DEVICE_ACTION_PROBE in idle! 164s (process:4117): libfprint-device-DEBUG: 20:26:12.905: Not updating temperature model, device can run continuously! 164s (process:4117): libfprint-realtek-DEBUG: 20:26:12.906: 132701841: ../libfprint/drivers/realtek/realtek.c:1270 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.906: [realtek] Init entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.907: [realtek] Init entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.908: [realtek] Init entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.908: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.908: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.908: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.909: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.910: [realtek] Init completed successfully 164s (process:4117): libfprint-realtek-DEBUG: 20:26:12.910: Init complete! 164s (process:4117): libfprint-device-DEBUG: 20:26:12.910: Device reported open completion 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.910: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-device-DEBUG: 20:26:12.910: Completing action FPI_DEVICE_ACTION_OPEN in idle! 164s (process:4117): libfprint-device-DEBUG: 20:26:12.910: Not updating temperature model, device can run continuously! 164s (process:4117): libfprint-realtek-DEBUG: 20:26:12.910: 132705897: ../libfprint/drivers/realtek/realtek.c:1333 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-realtek-DEBUG: 20:26:12.911: Successfully cleared storage 164s (process:4117): libfprint-device-DEBUG: 20:26:12.911: Device reported deletion completion 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.911: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-device-DEBUG: 20:26:12.911: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 164s (process:4117): libfprint-device-DEBUG: 20:26:12.911: Not updating temperature model, device can run continuously! 164s (process:4117): libfprint-device-DEBUG: 20:26:12.911: Not updating temperature model, device can run continuously! 164s (process:4117): libfprint-realtek-DEBUG: 20:26:12.911: 132707522: ../libfprint/drivers/realtek/realtek.c:1202 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.911: [realtek] Enroll entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.911: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.912: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.912: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.913: [realtek] Enroll entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.913: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.913: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.913: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.913: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.914: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.914: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.914: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.915: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.916: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.916: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.916: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.917: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.917: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.917: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.917: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.918: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.918: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.919: Device reported enroll progress, reported 1 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.919: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.919: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.919: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.919: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.919: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.920: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.920: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.920: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.920: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.921: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.921: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.921: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.921: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.921: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.922: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.922: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.922: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.922: Device reported enroll progress, reported 2 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.922: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.922: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.922: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.923: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.923: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.923: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.923: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.923: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.924: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.924: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.924: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.925: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.925: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.925: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.925: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.925: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.926: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.926: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.926: Device reported enroll progress, reported 3 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.926: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.926: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.926: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.927: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.927: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.927: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.927: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.927: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.928: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.928: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.928: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.929: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.929: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.929: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.929: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.929: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.930: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.930: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.930: Device reported enroll progress, reported 4 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.930: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.930: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.930: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.931: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.931: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.931: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.931: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.931: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.932: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.932: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.933: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.933: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.933: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.933: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.933: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.934: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.934: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.934: Device reported enroll progress, reported 5 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.934: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.934: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.934: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.934: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.935: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.935: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.935: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.935: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.935: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.936: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.936: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.937: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.937: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.937: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.937: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.937: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.938: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.938: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.938: Device reported enroll progress, reported 6 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.938: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.938: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.938: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.938: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.939: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.939: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.939: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.939: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.939: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.940: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.940: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.941: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.941: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.941: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.941: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.941: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.942: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.942: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.942: Device reported enroll progress, reported 7 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.942: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.942: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.942: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.942: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.942: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.942: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.943: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.943: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.943: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.943: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.944: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.944: Device reported finger status change: FP_FINGER_STATUS_PRESENT 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.944: [realtek] Enroll entering state 4 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.944: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.945: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.945: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.945: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.946: Device reported finger status change: FP_FINGER_STATUS_NONE 164s (process:4117): libfprint-device-DEBUG: 20:26:12.946: Device reported enroll progress, reported 8 of 8 have been completed 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.946: [realtek] Enroll entering state 2 164s (process:4117): libfprint-device-DEBUG: 20:26:12.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.946: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.946: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.946: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.946: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.947: [realtek] Enroll entering state 3 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.947: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 164s (process:4117): libfprint-SSM-DEBUG: 20:26:12.947: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.947: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.948: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.948: Device reported finger status change: FP_FINGER_STATUS_PRESENT 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.948: [realtek] Enroll entering state 4 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.948: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.949: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.949: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.949: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.950: Device reported finger status change: FP_FINGER_STATUS_NONE 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.950: [realtek] Enroll entering state 5 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.950: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.950: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.950: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.951: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.951: [realtek] Enroll entering state 6 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.951: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.951: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.951: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.952: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.952: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.952: [realtek] Enroll completed successfully 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.952: Enrollment complete! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.952: Device reported enroll completion 165s (process:4117): libfprint-device-DEBUG: 20:26:12.952: Print for finger FP_FINGER_UNKNOWN enrolled 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.952: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-device-DEBUG: 20:26:12.953: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.953: Not updating temperature model, device can run continuously! 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.953: 132748692: ../libfprint/drivers/realtek/realtek.c:1345 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.953: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.953: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.953: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.954: Query templates complete! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.954: Device reported listing completion 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.954: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-device-DEBUG: 20:26:12.954: Completing action FPI_DEVICE_ACTION_LIST in idle! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.954: Not updating temperature model, device can run continuously! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.954: Not updating temperature model, device can run continuously! 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.954: 132750229: ../libfprint/drivers/realtek/realtek.c:1178 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.954: [realtek] Verify & Identify entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.954: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.954: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.955: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.955: [realtek] Verify & Identify entering state 1 165s (process:4117): libfprint-device-DEBUG: 20:26:12.955: Device reported finger status change: FP_FINGER_STATUS_NEEDED 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.955: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.956: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.956: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.956: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.956: [realtek] Verify & Identify entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.956: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.957: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.957: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.957: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.958: Device reported finger status change: FP_FINGER_STATUS_PRESENT 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.958: [realtek] Verify & Identify entering state 3 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.958: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.958: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.958: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.959: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.959: Device reported finger status change: FP_FINGER_STATUS_NONE 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.959: [realtek] Verify & Identify entering state 4 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.959: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.960: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.960: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.960: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.961: Device reported verify result 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.961: [realtek] Verify & Identify entering state 5 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.961: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.961: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.961: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.961: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.962: [realtek] Verify & Identify completed successfully 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.962: Verify complete! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.962: Device reported verify completion 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.962: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-device-DEBUG: 20:26:12.962: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.962: Not updating temperature model, device can run continuously! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.962: Not updating temperature model, device can run continuously! 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.962: 132758204: ../libfprint/drivers/realtek/realtek.c:1178 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.962: [realtek] Verify & Identify entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.962: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.963: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.963: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.964: [realtek] Verify & Identify entering state 1 165s (process:4117): libfprint-device-DEBUG: 20:26:12.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.964: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.964: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.964: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.964: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.965: [realtek] Verify & Identify entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.965: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.965: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.965: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.965: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.966: Device reported finger status change: FP_FINGER_STATUS_PRESENT 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.966: [realtek] Verify & Identify entering state 3 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.966: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.966: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.966: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.967: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.967: Device reported finger status change: FP_FINGER_STATUS_NONE 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.967: [realtek] Verify & Identify entering state 4 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.967: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.968: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.968: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.968: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-device-DEBUG: 20:26:12.969: Device reported identify result 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.969: [realtek] Verify & Identify completed successfully 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.969: Verify complete! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.969: Device reported identify completion 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.969: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-device-DEBUG: 20:26:12.969: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.969: Not updating temperature model, device can run continuously! 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.969: 132765189: ../libfprint/drivers/realtek/realtek.c:1314 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.969: [realtek] Delete print entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.969: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.970: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.970: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.971: [realtek] Delete print entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.971: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.971: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.971: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.971: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.971: [realtek] Delete print completed successfully 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.971: Delete print complete! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.971: Device reported deletion completion 165s (process:4117): libfprint-SSM-DEBUG: 20:26:12.971: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 165s (process:4117): libfprint-device-DEBUG: 20:26:12.971: Completing action FPI_DEVICE_ACTION_DELETE in idle! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.971: Not updating temperature model, device can run continuously! 165s (process:4117): libfprint-realtek-DEBUG: 20:26:12.972: 132767636: ../libfprint/drivers/realtek/realtek.c:1302 165s (process:4117): libfprint-device-DEBUG: 20:26:12.972: Device reported close completion 165s (process:4117): libfprint-device-DEBUG: 20:26:12.972: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 165s (process:4117): libfprint-device-DEBUG: 20:26:12.972: Not updating temperature model, device can run continuously! 165s enrolling 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 1, None, None, None) 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 2, None, None, None) 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 3, None, None, None) 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 4, None, None, None) 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 5, None, None, None) 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 6, None, None, None) 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 7, None, None, None) 165s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x7187aa1d6400 (FpiDeviceRealtek at 0x17a54c20)>, 8, None, None, None) 165s enroll done 165s listing 165s listing done 165s verifying 165s verify done 165s async identifying 165s indentification_done: 165s deleting 165s delete done 165s ** (umockdev-run:4113): DEBUG: 20:26:12.987: umockdev.vala:154: Removing test bed /tmp/umockdev.IRAH22 165s (umockdev-run:4113): GLib-DEBUG: 20:26:12.993: unsetenv() is not thread-safe and should not be used after threads are created 165s PASS: libfprint-2/driver-realtek-5816.test 165s Running test: libfprint-2/driver-elanspi.test 165s ** (umockdev-run:4125): DEBUG: 20:26:13.035: umockdev.vala:127: Created udev test bed /tmp/umockdev.Y5A012 165s ** (umockdev-run:4125): DEBUG: 20:26:13.036: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 165s ** (umockdev-run:4125): DEBUG: 20:26:13.036: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00/spidev/spidev0.0 (subsystem spidev) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.037: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.Y5A012/dev/spidev0.0: got pty /dev/pts/0 165s ** (umockdev-run:4125): DEBUG: 20:26:13.037: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.Y5A012/dev/.ptymap/_dev_pts_0 165s ** (umockdev-run:4125): DEBUG: 20:26:13.037: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 165s ** (umockdev-run:4125): DEBUG: 20:26:13.038: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.040: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 165s ** (umockdev-run:4125): DEBUG: 20:26:13.041: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.043: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 165s ** (umockdev-run:4125): DEBUG: 20:26:13.043: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.044: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2 165s ** (umockdev-run:4125): DEBUG: 20:26:13.044: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.046: umockdev.vala:1414: 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 165s ** (umockdev-run:4125): DEBUG: 20:26:13.046: umockdev.vala:1492: 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) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.047: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.Y5A012/dev/hidraw0: got pty /dev/pts/1 165s ** (umockdev-run:4125): DEBUG: 20:26:13.047: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.Y5A012/dev/.ptymap/_dev_pts_1 165s ** (umockdev-run:4125): DEBUG: 20:26:13.047: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 165s ** (umockdev-run:4125): DEBUG: 20:26:13.047: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00/0018:04F3:3057.0001 (subsystem hid) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.048: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 165s ** (umockdev-run:4125): DEBUG: 20:26:13.049: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.049: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 165s ** (umockdev-run:4125): DEBUG: 20:26:13.050: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.050: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 165s ** (umockdev-run:4125): DEBUG: 20:26:13.050: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 165s ** (umockdev-run:4125): DEBUG: 20:26:13.051: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1 165s ** (umockdev-run:4125): DEBUG: 20:26:13.051: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 165s (umockdev-run:4125): GLib-GIO-DEBUG: 20:26:13.053: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 165s (process:4129): libfprint-context-DEBUG: 20:26:13.162: Initializing FpContext (libfprint version 1.94.8+tod1) 165s (process:4129): libfprint-tod-DEBUG: 20:26:13.162: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 165s (process:4129): libfprint-device-DEBUG: 20:26:13.165: Device reported probe completion 165s (process:4129): libfprint-device-DEBUG: 20:26:13.165: Completing action FPI_DEVICE_ACTION_PROBE in idle! 165s (process:4129): libfprint-device-DEBUG: 20:26:13.165: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.166: 132962106: ../libfprint/drivers/elanspi.c:1562 165s (process:4129): libfprint-image_device-DEBUG: 20:26:13.166: Image device open completed 165s (process:4129): libfprint-device-DEBUG: 20:26:13.166: Device reported open completion 165s (process:4129): libfprint-device-DEBUG: 20:26:13.166: Completing action FPI_DEVICE_ACTION_OPEN in idle! 165s (process:4129): libfprint-device-DEBUG: 20:26:13.166: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (process:4129): libfprint-device-DEBUG: 20:26:13.166: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 165s (process:4129): libfprint-image_device-DEBUG: 20:26:13.166: Activating image device 165s (process:4129): libfprint-image_device-DEBUG: 20:26:13.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.166: [elanspi] ELANSPI_INIT_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.167: [elanspi] ELANSPI_INIT_NSTATES entering state 1 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.167: got status 81 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.167: sync hw reset 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.167: [elanspi] ELANSPI_INIT_NSTATES entering state 2 165s libfprint-Message: 20:26:13.166: Failed to read spidev block size, using 4096 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.171: [elanspi] ELANSPI_INIT_NSTATES entering state 3 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.171: sw reset ok 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.172: [elanspi] ELANSPI_INIT_NSTATES entering state 4 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.172: raw height = 96 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.172: [elanspi] ELANSPI_INIT_NSTATES entering state 5 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.172: raw width = 96 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.172: [elanspi] ELANSPI_INIT_NSTATES entering state 6 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.172: raw reg17 = 175 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.173: [elanspi] ELANSPI_INIT_NSTATES entering state 7 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.173: raw version = 09 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.173: after hardcoded lookup; 96x96, version 1 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.173: found sensor ID 6 => [eFSA96SA] (96 x 96) 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.173: [elanspi] ELANSPI_INIT_NSTATES entering state 8 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.177: [elanspi] ELANSPI_INIT_NSTATES entering state 9 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.177: [elanspi] ELANSPI_INIT_NSTATES entering state 10 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.177: [elanspi] ELANSPI_INIT_NSTATES entering state 11 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.178: [elanspi] ELANSPI_INIT_NSTATES entering state 12 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.178: [elanspi] ELANSPI_INIT_NSTATES entering state 13 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.178: [elanspi] ELANSPI_INIT_NSTATES entering state 14 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.178: [elanspi] ELANSPI_INIT_NSTATES entering state 17 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.178: got vcm mode = 2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.178: [elanspi] ELANSPI_INIT_NSTATES entering state 18 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.179: [elanspi] ELANSPI_INIT_NSTATES entering state 19 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.179: starting calibrate 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.179: [elanspi] old calibrate entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.180: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.180: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.180: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.180: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.180: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.181: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.182: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.183: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.184: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.185: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.237: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.237: dac init is 0x29 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.238: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-device-DEBUG: 20:26:13.266: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.300: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.301: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.368: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.368: calibration ok, saving bg image 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.369: [elanspi] old calibrate completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.369: [elanspi] ELANSPI_INIT_NSTATES entering state 20 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.369: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.435: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.436: [elanspi] ELANSPI_INIT_NSTATES entering state 21 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.436: [elanspi] ELANSPI_INIT_NSTATES completed successfully 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.436: 133231636: ../libfprint/drivers/elanspi.c:1596 165s (process:4129): libfprint-image_device-DEBUG: 20:26:13.436: Image device activation completed 165s (process:4129): libfprint-image_device-DEBUG: 20:26:13.436: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 165s (process:4129): libfprint-image_device-DEBUG: 20:26:13.436: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.436: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.436: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.436: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.436: started capturer 165s (process:4129): libfprint-device-DEBUG: 20:26:13.436: Device reported finger status change: FP_FINGER_STATUS_NEEDED 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.496: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.496: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.496: stddev=933d, ip=40, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.496: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.496: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.563: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.563: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.563: stddev=829d, ip=48, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.563: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.563: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.630: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.630: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.630: stddev=1307d, ip=37, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.630: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.630: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.695: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.695: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.695: stddev=1163d, ip=38, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.695: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.695: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.758: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.758: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.759: stddev=960d, ip=43, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.759: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.759: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.816: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.817: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.817: stddev=879d, ip=41, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.817: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.817: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.877: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.877: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.878: stddev=925d, ip=44, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.878: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.878: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.941: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.941: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 165s (process:4129): libfprint-elanspi-DEBUG: 20:26:13.941: stddev=1244d, ip=37, is_fp=0, is_empty=2 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.941: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 165s (process:4129): libfprint-SSM-DEBUG: 20:26:13.941: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.007: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.007: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.008: stddev=709d, ip=48, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.008: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.008: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.069: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.069: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.069: stddev=553d, ip=54, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.069: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.069: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.129: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.129: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.130: stddev=904d, ip=44, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.130: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.130: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.189: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.189: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.189: stddev=951d, ip=46, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.189: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.189: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.256: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.256: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.256: stddev=795d, ip=44, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.256: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.256: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.327: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.327: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.327: stddev=985d, ip=41, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.327: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.327: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.398: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.398: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.398: stddev=938d, ip=40, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.398: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.398: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.461: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.461: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.461: stddev=846d, ip=40, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.461: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.461: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.521: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.521: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.521: stddev=693d, ip=56, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.521: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.521: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.582: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.582: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.582: stddev=777d, ip=50, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.582: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.582: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.643: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.643: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.644: stddev=824d, ip=45, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.644: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.644: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.704: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.704: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.704: stddev=521d, ip=50, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.704: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.704: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.768: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.768: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.768: stddev=670d, ip=47, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.768: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.768: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.829: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.829: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.829: stddev=1262d, ip=39, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.829: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.829: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.899: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.899: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 166s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.899: stddev=912d, ip=42, is_fp=0, is_empty=2 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.899: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 166s (process:4129): libfprint-SSM-DEBUG: 20:26:14.899: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:14.961: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:14.961: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:14.961: stddev=1402d, ip=37, is_fp=0, is_empty=2 167s (process:4129): libfprint-SSM-DEBUG: 20:26:14.961: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 167s (process:4129): libfprint-SSM-DEBUG: 20:26:14.961: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.023: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.023: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.023: stddev=1530d, ip=32, is_fp=0, is_empty=2 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.023: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.023: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.082: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.082: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.082: stddev=718159d, ip=6, is_fp=1, is_empty=0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.082: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.082: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.144: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.144: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.144: stddev=400929d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-device-DEBUG: 20:26:15.144: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 167s (process:4129): libfprint-image_device-DEBUG: 20:26:15.144: Image device reported finger status: on 167s (process:4129): libfprint-image_device-DEBUG: 20:26:15.144: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.144: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.144: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.205: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.205: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.206: stddev=346514d, ip=0, is_fp=1, is_empty=0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.206: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.206: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.256: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.256: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.256: stddev=324160d, ip=0, is_fp=1, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.257: diff = 107344 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.257: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.257: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.305: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.305: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.305: stddev=339430d, ip=0, is_fp=1, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.305: diff = 246471 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.305: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.305: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.352: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.352: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.352: stddev=334711d, ip=0, is_fp=1, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.353: diff = 73010 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.353: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.353: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.401: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.401: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.401: stddev=317574d, ip=0, is_fp=1, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.402: diff = 58831 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.402: ignoring b.c. difference is too small 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.402: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.402: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.453: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.454: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.454: stddev=285577d, ip=0, is_fp=1, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.455: diff = 241923 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.455: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.455: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.501: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.501: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.501: stddev=417772d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.502: diff = 254823 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.502: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.502: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.550: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.550: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.550: stddev=541148d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.550: diff = 290922 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.550: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.550: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.603: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.603: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.603: stddev=580192d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.604: diff = 332283 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.604: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.604: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.661: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.661: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.661: stddev=484527d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.662: diff = 325141 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.662: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.662: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.717: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.717: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.717: stddev=482100d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.718: diff = 337412 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.718: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.718: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.778: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.778: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.778: stddev=558238d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.779: diff = 342841 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.779: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.779: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.835: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.835: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.836: stddev=572990d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.836: diff = 352690 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.836: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.836: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.893: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.893: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.893: stddev=575411d, ip=0, is_fp=2, is_empty=0 167s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.894: diff = 365537 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.894: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 167s (process:4129): libfprint-SSM-DEBUG: 20:26:15.894: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:15.955: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:15.955: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.955: stddev=578482d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:15.956: diff = 342041 168s (process:4129): libfprint-SSM-DEBUG: 20:26:15.956: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:15.956: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.011: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.011: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.011: stddev=572686d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.012: diff = 421037 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.012: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.012: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.069: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.069: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.069: stddev=465498d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.070: diff = 404640 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.070: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.070: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.129: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.129: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.129: stddev=410135d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.131: diff = 347658 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.131: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.131: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.189: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.189: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.189: stddev=493239d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.190: diff = 344237 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.190: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.190: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.246: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.246: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.247: stddev=553028d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.247: diff = 419597 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.247: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.247: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.303: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.303: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.303: stddev=574502d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.304: diff = 408934 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.304: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.304: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.360: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.360: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.360: stddev=645815d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.361: diff = 409198 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.361: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.361: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.417: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.417: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.417: stddev=677451d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.418: diff = 429666 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.418: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.418: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.474: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.474: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.475: stddev=634407d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.475: have enough frames, exiting now 168s (process:4129): libfprint-assembling-DEBUG: 20:26:16.551: calc delta completed in 0.076132 secs 168s (process:4129): libfprint-assembling-DEBUG: 20:26:16.628: calc delta completed in 0.076668 secs 168s (process:4129): libfprint-assembling-DEBUG: 20:26:16.628: errors: 86516 rev: 170625 168s (process:4129): libfprint-assembling-DEBUG: 20:26:16.704: calc delta completed in 0.075765 secs 168s (process:4129): libfprint-assembling-DEBUG: 20:26:16.704: height is 246 168s (process:4129): libfprint-image_device-DEBUG: 20:26:16.706: Image device captured an image 168s (process:4129): libfprint-image_device-DEBUG: 20:26:16.706: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 168s (process:4129): libfprint-device-DEBUG: 20:26:16.706: Device reported finger status change: FP_FINGER_STATUS_PRESENT 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.706: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.706: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-image-DEBUG: 20:26:16.750: Minutiae scan completed in 0.041695 secs 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.752: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.752: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.752: stddev=593525d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.752: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.752: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.799: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.799: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.799: stddev=610651d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.799: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.799: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.845: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.845: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.845: stddev=505673d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.845: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.845: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.893: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.893: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 168s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.894: stddev=537580d, ip=0, is_fp=2, is_empty=0 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.894: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 168s (process:4129): libfprint-SSM-DEBUG: 20:26:16.894: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.943: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.943: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.944: stddev=520750d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.944: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.944: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.992: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.992: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:16.992: stddev=468008d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.992: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:16.992: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.039: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.039: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.039: stddev=477058d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.039: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.039: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.087: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.087: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.087: stddev=460178d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.087: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.087: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.134: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.134: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.134: stddev=538508d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.134: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.134: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.181: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.181: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.182: stddev=661673d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.182: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.182: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s Executing: libfprint-2/driver-elanspi.test 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.230: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.230: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.230: stddev=764706d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.230: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.230: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.281: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.281: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.281: stddev=806415d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.281: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.281: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.330: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.330: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.330: stddev=806649d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.330: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.330: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.379: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.379: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.379: stddev=822567d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.379: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.379: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.426: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.426: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.427: stddev=1017068d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.427: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.427: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.474: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.474: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.474: stddev=1004196d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.474: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.474: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.520: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.520: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.521: stddev=963655d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.521: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.521: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.567: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.567: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.567: stddev=880521d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.567: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.567: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.615: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.615: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.616: stddev=1135372d, ip=0, is_fp=2, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.616: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.616: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.664: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.664: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.664: stddev=1093450d, ip=3, is_fp=1, is_empty=0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.664: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.664: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.710: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.710: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.711: stddev=41090d, ip=8, is_fp=0, is_empty=2 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.711: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.711: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.763: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.763: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 169s (process:4129): libfprint-elanspi-DEBUG: 20:26:17.763: stddev=6836d, ip=13, is_fp=0, is_empty=2 169s (process:4129): libfprint-device-DEBUG: 20:26:17.763: Device reported finger status change: FP_FINGER_STATUS_NONE 169s (process:4129): libfprint-image_device-DEBUG: 20:26:17.763: Image device reported finger status: off 169s (process:4129): libfprint-image_device-DEBUG: 20:26:17.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 169s (process:4129): libfprint-image_device-DEBUG: 20:26:17.763: Deactivating image device 169s (process:4129): libfprint-image_device-DEBUG: 20:26:17.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 169s (process:4129): libfprint-image_device-DEBUG: 20:26:17.763: Image device deactivation completed 169s (process:4129): libfprint-image_device-DEBUG: 20:26:17.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 169s (process:4129): libfprint-device-DEBUG: 20:26:17.763: Device reported capture completion 169s (process:4129): libfprint-SSM-DEBUG: 20:26:17.763: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 169s (process:4129): libfprint-device-DEBUG: 20:26:17.763: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 169s (process:4129): libfprint-device-DEBUG: 20:26:17.763: Updated temperature model after 4.50 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s (process:4129): libfprint-image_device-DEBUG: 20:26:17.765: Image device close completed 169s (process:4129): libfprint-device-DEBUG: 20:26:17.765: Device reported close completion 169s (process:4129): libfprint-device-DEBUG: 20:26:17.766: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 169s (process:4129): libfprint-device-DEBUG: 20:26:17.766: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 169s ** (umockdev-run:4125): DEBUG: 20:26:17.935: umockdev.vala:154: Removing test bed /tmp/umockdev.Y5A012 170s (umockdev-run:4125): GLib-DEBUG: 20:26:17.945: unsetenv() is not thread-safe and should not be used after threads are created 170s Comparing PNGs /tmp/libfprint-umockdev-test-bwsnkl9w/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 170s PASS: libfprint-2/driver-elanspi.test 170s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 170s (process:4138): libfprint-context-DEBUG: 20:26:17.998: Initializing FpContext (libfprint version 1.94.8+tod1) 170s (process:4138): libfprint-tod-DEBUG: 20:26:17.998: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 170s (process:4138): libfprint-tod-DEBUG: 20:26:17.998: Found TOD entry point symbol 0x7eb6fe7e14b0, GType is 106920374989664 170s (process:4138): libfprint-tod-DEBUG: 20:26:17.998: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 170s (process:4138): libfprint-context-DEBUG: 20:26:17.999: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 170s (process:4138): libfprint-context-DEBUG: 20:26:17.999: created 170s (process:4138): libfprint-fake_test_dev_tod_current-DEBUG: 20:26:17.999: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 170s 170s (process:4138): libfprint-device-DEBUG: 20:26:17.999: Device reported probe completion 170s (process:4138): libfprint-device-DEBUG: 20:26:17.999: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s (process:4138): libfprint-device-DEBUG: 20:26:17.999: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s (/usr/libexec/installed-tests/libfprint-2/test-fpi-device-tod:4138): GLib-DEBUG: 20:26:17.999: setenv()/putenv() are not thread-safe and should not be used after threads are created 170s TAP version 14 170s # random seed: R02S9e16d07b87e3d098f2caad2b4f3f5bca 170s 1..97 170s # Start of driver tests 170s ok 1 /driver/get_driver 170s ok 2 /driver/get_device_id 170s ok 3 /driver/get_name 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 4 /driver/is_open 170s ok 5 /driver/get_nr_enroll_stages 170s ok 6 /driver/set_nr_enroll_stages 170s ok 7 /driver/supports_identify 170s ok 8 /driver/supports_capture 170s ok 9 /driver/has_storage 170s ok 10 /driver/do_not_support_identify 170s ok 11 /driver/do_not_support_capture 170s ok 12 /driver/has_not_storage 170s ok 13 /driver/get_usb_device 170s ok 14 /driver/get_virtual_env 170s ok 15 /driver/get_driver_data 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 170s # 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 16 /driver/initial_features 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 170s # 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 17 /driver/probe 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 18 /driver/open 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 19 /driver/close 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 20 /driver/enroll 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 21 /driver/verify 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 22 /driver/identify 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 170s # 170s # libfprint-device-DEBUG: Device reported capture completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 23 /driver/capture 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 170s # 170s # libfprint-device-DEBUG: Device reported listing completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 24 /driver/list 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 170s # 170s # libfprint-device-DEBUG: Device reported deletion completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 25 /driver/delete 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 170s # 170s # libfprint-device-DEBUG: Device reported deletion completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 26 /driver/clear_storage 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 170s # 170s # libfprint-device-DEBUG: Device reported deletion completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 27 /driver/cancel 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 28 /driver/critical 170s ok 29 /driver/get_current_action 170s ok 30 /driver/timeout 170s ok 31 /driver/error_types 170s ok 32 /driver/retry_error_types 170s # Start of get_scan_type tests 170s ok 33 /driver/get_scan_type/press 170s ok 34 /driver/get_scan_type/swipe 170s # End of get_scan_type tests 170s # Start of set_scan_type tests 170s ok 35 /driver/set_scan_type/press 170s ok 36 /driver/set_scan_type/swipe 170s # End of set_scan_type tests 170s # Start of finger_status tests 170s ok 37 /driver/finger_status/inactive 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 170s ok 38 /driver/finger_status/waiting 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 170s ok 39 /driver/finger_status/present 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 170s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 170s ok 40 /driver/finger_status/changes 170s # End of finger_status tests 170s # Start of features tests 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 170s # 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 41 /driver/features/probe_updates 170s # End of features tests 170s # Start of initial_features tests 170s ok 42 /driver/initial_features/none 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 43 /driver/initial_features/no_capture 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 44 /driver/initial_features/no_verify 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 45 /driver/initial_features/no_identify 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 46 /driver/initial_features/no_storage 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 47 /driver/initial_features/no_list 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s ok 48 /driver/initial_features/no_delete 170s ok 49 /driver/initial_features/no_clear 170s # End of initial_features tests 170s # Start of probe tests 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 50 /driver/probe/error 170s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 170s # libfprint-device-DEBUG: Device reported probe completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 51 /driver/probe/action_error 170s # End of probe tests 170s # Start of open tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 52 /driver/open/error 170s # End of open tests 170s # Start of close tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 53 /driver/close/error 170s # End of close tests 170s # Start of enroll tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 54 /driver/enroll/error 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported enroll progress, reported 1936330083 of 786302597 have been completed 170s # libfprint-device-DEBUG: Device reported enroll progress, reported 1953127866 of 786302597 have been completed 170s # libfprint-device-DEBUG: Device reported enroll progress, reported 1121484254 of 786302597 have been completed 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 55 /driver/enroll/progress 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 170s # 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 56 /driver/enroll/update_nbis 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 57 /driver/enroll/update_nbis_wrong_device 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 58 /driver/enroll/update_nbis_wrong_driver 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 59 /driver/enroll/update_nbis_missing_feature 170s # Start of error tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported enroll completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 60 /driver/enroll/error/no_print 170s # End of error tests 170s # End of enroll tests 170s # Start of verify tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 61 /driver/verify/fail 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 62 /driver/verify/retry 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 170s # 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 63 /driver/verify/error 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 64 /driver/verify/not_supported 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 65 /driver/verify/report_no_cb 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 66 /driver/verify/not_reported 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported verify result 170s # libfprint-device-DEBUG: Device reported verify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 67 /driver/verify/complete_retry 170s # End of verify tests 170s # Start of identify tests 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 68 /driver/identify/fail 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 69 /driver/identify/retry 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 70 /driver/identify/error 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 170s ok 71 /driver/identify/not_reported 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 72 /driver/identify/complete_retry 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 73 /driver/identify/report_no_cb 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 74 /driver/identify/suspend_continues 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify result 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 75 /driver/identify/suspend_succeeds 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 170s # 170s # libfprint-device-DEBUG: Device reported identify completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 170s ok 76 /driver/identify/suspend_busy_error 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 170s # 170s # libfprint-device-DEBUG: Device reported close completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s ok 77 /driver/identify/suspend_while_idle 170s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 170s # libfprint-device-DEBUG: Tod version info is 'current' 170s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 170s # 170s # libfprint-device-DEBUG: Device reported open completion 170s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 170s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 172s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 172s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 172s # 172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 172s # 172s # libfprint-device-DEBUG: Device reported identify completion 172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 174s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 174s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 78 /driver/identify/warmup_cooldown 177s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 177s # End of identify tests 177s # Start of capture tests 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 79 /driver/capture/not_supported 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 177s # 177s # libfprint-device-DEBUG: Device reported capture completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s ok 80 /driver/capture/error 177s # End of capture tests 177s # Start of list tests 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 177s # 177s # libfprint-device-DEBUG: Device reported listing completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 81 /driver/list/error 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 82 /driver/list/no_storage 177s # End of list tests 177s # Start of delete tests 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 177s # 177s # libfprint-device-DEBUG: Device reported deletion completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 83 /driver/delete/error 177s # End of delete tests 177s # Start of clear_storage tests 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 177s # libfprint-device-DEBUG: Tod version info is 'current' 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 177s # 177s # libfprint-device-DEBUG: Device reported deletion completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 84 /driver/clear_storage/error 177s # End of clear_storage tests 177s # Start of cancel tests 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 177s # 177s # libfprint-device-DEBUG: Device reported deletion completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 85 /driver/cancel/fail 177s # End of cancel tests 177s # Start of get_current_action tests 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 86 /driver/get_current_action/open 177s # End of get_current_action tests 177s # Start of get_cancellable tests 177s ok 87 /driver/get_cancellable/error 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 88 /driver/get_cancellable/open 177s # Start of open tests 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 89 /driver/get_cancellable/open/internal 177s # End of open tests 177s # End of get_cancellable tests 177s # Start of action_is_cancelled tests 177s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 177s # libfprint-device-DEBUG: Tod version info is 'current' 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 90 /driver/action_is_cancelled/open 177s ok 91 /driver/action_is_cancelled/error 177s # Start of open tests 177s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 177s # libfprint-device-DEBUG: Tod version info is 'current' 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s ok 92 /driver/action_is_cancelled/open/internal 177s # End of open tests 177s # End of action_is_cancelled tests 177s # Start of complete_action tests 177s # Start of all tests 177s ok 93 /driver/complete_action/all/error 177s # End of all tests 177s # End of complete_action tests 177s # Start of action_error tests 177s ok 94 /driver/action_error/error 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 177s # libfprint-device-DEBUG: Device reported enroll completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 177s # libfprint-device-DEBUG: Device reported verify completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 177s # libfprint-device-DEBUG: Device reported identify completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 177s # libfprint-device-DEBUG: Device reported capture completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 177s # libfprint-device-DEBUG: Device reported listing completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 177s # libfprint-device-DEBUG: Device reported deletion completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 177s # libfprint-device-DEBUG: Tod version info is 'current' 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 177s # libfprint-device-DEBUG: Device reported deletion completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s ok 95 /driver/action_error/all 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 177s # 177s # libfprint-device-DEBUG: Device reported open completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 177s # 177s # libfprint-device-DEBUG: Device reported enroll completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 177s # 177s # libfprint-device-DEBUG: Device reported verify completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 177s # 177s # libfprint-device-DEBUG: Device reported identify completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 177s # 177s # libfprint-device-DEBUG: Device reported capture completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 177s # 177s # libfprint-device-DEBUG: Device reported listing completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 177s # 177s # libfprint-device-DEBUG: Device reported deletion completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 177s # libfprint-device-DEBUG: Tod version info is 'current' 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 177s # 177s # libfprint-device-DEBUG: Device reported deletion completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 177s # 177s # libfprint-device-DEBUG: Device reported close completion 177s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 177s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 177s ok 96 /driver/action_error/fail 177s # End of action_error tests 177s # Start of timeout tests 177s ok 97 /driver/timeout/cancelled 177s # End of timeout tests 177s # End of driver tests 177s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 177s Running test: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.2.test 177s TAP version 14 177s # random seed: R02Sa316733e53f1bedb1206101207a26f93 177s 1..4 177s # Start of context tests 177s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 177s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 177s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x750a39c9e987, GType is 93988610284944 177s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 177s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.2 177s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 177s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x750a39c9853b, GType is 93988610289744 177s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 177s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.2 177s ok 1 /context/new 177s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 177s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 177s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 177s ok 2 /context/no-devices 177s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 177s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 177s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x750a39c9e987, GType is 93988610284944 177s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 177s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 177s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x750a39c9853b, GType is 93988610289744 177s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 177s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 177s # libfprint-context-DEBUG: created 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM_SINGLE_STATE entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM_SINGLE_STATE completed successfully 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 14 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state -10 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 177s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 14 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state -10 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 178s # libfprint-device-DEBUG: Device reported probe completion 178s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 178s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 178s ok 3 /context/has-virtual-device # SKIP Not supported by TODv1 older than 1.92 178s # slow test /context/has-virtual-device executed in 1.03 secs 178s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 178s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 178s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x750a39c9e987, GType is 93988610284944 178s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 178s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 178s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x750a39c9853b, GType is 93988610289744 178s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 178s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 178s # libfprint-context-DEBUG: created 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM_SINGLE_STATE entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM_SINGLE_STATE completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 14 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state -10 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 178s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 179s Executing: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.2.test 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 2 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 3 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 14 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state -10 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM cancelled delayed state change 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.2] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 179s # libfprint-device-DEBUG: Device reported probe completion 179s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 179s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 179s ok 4 /context/enumerates-new-devices # SKIP Not supported by TODv1 older than 1.92 179s # slow test /context/enumerates-new-devices executed in 1.03 secs 179s # End of context tests 179s PASS: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.2.test 179s Running test: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.5.test 179s TAP version 14 179s # random seed: R02S9187b7e7bb110fe772db70e8b6788ff5 179s 1..4 179s # Start of context tests 179s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 179s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 179s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7175b0da553b, GType is 108676324056880 179s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 179s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.5 179s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 179s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7175b0d90987, GType is 108676324061680 179s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 179s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.5 179s ok 1 /context/new 179s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 179s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 179s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 179s ok 2 /context/no-devices 179s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 179s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 179s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7175b0da553b, GType is 108676324056880 179s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 179s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 179s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7175b0d90987, GType is 108676324061680 179s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 179s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 179s # libfprint-context-DEBUG: created 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM_SINGLE_STATE entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM_SINGLE_STATE completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 14 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state -10 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 179s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 14 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state -10 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 180s # libfprint-device-DEBUG: Device reported probe completion 180s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 180s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 180s ok 3 /context/has-virtual-device # SKIP Not supported by TODv1 older than 1.92 180s # slow test /context/has-virtual-device executed in 1.03 secs 180s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-test-driver-v1+1.90.5-x86_64.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7175b0da553b, GType is 108676324056880 180s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.5 (Virtual device for debugging) 180s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.5/libdevice-fake-tod-ssm-test-v1+1.90.5-x86_64.so 180s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7175b0d90987, GType is 108676324061680 180s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.5 (Virtual device for SSM Testing) 180s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 180s # libfprint-context-DEBUG: created 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM_SINGLE_STATE entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM_SINGLE_STATE completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 14 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state -10 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 180s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 2 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 3 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 14 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state -10 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed successfully 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM cancelled delayed state change 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed successfully 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed successfully 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed successfully 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 1 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM entering state 0 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 181s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.90.5] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 181s # libfprint-device-DEBUG: Device reported probe completion 181s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 181s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s ok 4 /context/enumerates-new-devices # SKIP Not supported by TODv1 older than 1.92 181s # slow test /context/enumerates-new-devices executed in 1.03 secs 181s # End of context tests 181s PASS: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.90.5.test 181s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.94.1.test 181s TAP version 14 181s # random seed: R02S998777b4857aeb6cbdcf0b7848287132 181s 1..4 181s # Start of context tests 181s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 181s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 181s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7cc6bfd449d3, GType is 105775816592784 181s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 181s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 181s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7cc6bfd3eb7b, GType is 105775816597456 181s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 181s ok 1 /context/new 181s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 181s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 181s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 181s ok 2 /context/no-devices 181s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 181s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 181s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7cc6bfd449d3, GType is 105775816592784 181s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 181s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 181s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7cc6bfd3eb7b, GType is 105775816597456 181s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 181s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 181s # libfprint-context-DEBUG: created 181s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 181s # 181s # libfprint-device-DEBUG: Device reported probe completion 181s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 181s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 181s # 181s # libfprint-device-DEBUG: Device reported open completion 181s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 181s # 181s # libfprint-device-DEBUG: Device reported close completion 181s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 181s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s ok 3 /context/has-virtual-device 181s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 181s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-ssm-test-v1+1.94.1-x86_64.so 181s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7cc6bfd449d3, GType is 105775816592784 181s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.1 (Virtual device for SSM Testing) 181s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.1/libdevice-fake-tod-test-driver-v1+1.94.1-x86_64.so 181s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7cc6bfd3eb7b, GType is 105775816597456 181s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.1 (Virtual device for debugging) 181s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 181s # libfprint-context-DEBUG: created 181s # libfprint-fake_test_dev_tod_v1+1.94.1-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 181s # 181s # libfprint-device-DEBUG: Device reported probe completion 181s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 181s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s ok 4 /context/enumerates-new-devices 181s # End of context tests 181s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.94.1.test 181s Running test: libfprint-2/virtual-image.test 181s (process:4180): libfprint-context-DEBUG: 20:26:29.753: Initializing FpContext (libfprint version 1.94.8+tod1) 181s (process:4180): libfprint-tod-DEBUG: 20:26:29.753: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 181s (process:4180): libfprint-context-DEBUG: 20:26:29.754: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-edu2knb7/virtual-image.socket 181s (process:4180): libfprint-context-DEBUG: 20:26:29.754: created 181s (process:4180): libfprint-device-DEBUG: 20:26:29.755: Device reported probe completion 181s (process:4180): libfprint-device-DEBUG: 20:26:29.755: Completing action FPI_DEVICE_ACTION_PROBE in idle! 181s (process:4180): libfprint-device-DEBUG: 20:26:29.755: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:4180): libfprint-virtual_image-DEBUG: 20:26:29.760: 149556117: ../libfprint/drivers/virtual-image.c:216 181s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:29.760: 149556194: ../libfprint/drivers/virtual-device-listener.c:153 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.860: Image device open completed 181s (process:4180): libfprint-device-DEBUG: 20:26:29.860: Device reported open completion 181s (process:4180): libfprint-device-DEBUG: 20:26:29.861: Completing action FPI_DEVICE_ACTION_OPEN in idle! 181s (process:4180): libfprint-device-DEBUG: 20:26:29.861: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4180): libfprint-device-DEBUG: 20:26:29.861: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.861: Activating image device 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.861: Image device activation completed 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.861: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 181s (process:4180): libfprint-device-DEBUG: 20:26:29.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 181s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:29.862: Got a new connection! 181s (process:4180): libfprint-device-DEBUG: 20:26:29.862: Idle cancelling on ongoing operation! 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.862: Deactivating image device 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.862: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.862: Image device deactivation completed 181s (process:4180): libfprint-image_device-DEBUG: 20:26:29.862: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 181s (process:4180): libfprint-device-DEBUG: 20:26:29.862: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 181s (process:4180): libfprint-device-DEBUG: 20:26:29.862: Device reported capture completion 181s (process:4180): libfprint-device-DEBUG: 20:26:29.862: Device reported finger status change: FP_FINGER_STATUS_NONE 181s (process:4180): libfprint-device-DEBUG: 20:26:29.862: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 181s (process:4180): libfprint-device-DEBUG: 20:26:29.862: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 181s (process:4180): libfprint-virtual_image-DEBUG: 20:26:29.862: 149658528: ../libfprint/drivers/virtual-image.c:244 182s (process:4180): libfprint-image_device-DEBUG: 20:26:29.963: Image device close completed 182s (process:4180): libfprint-device-DEBUG: 20:26:29.963: Device reported close completion 182s (process:4180): libfprint-device-DEBUG: 20:26:29.963: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 182s (process:4180): libfprint-device-DEBUG: 20:26:29.963: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s Capture operation finished 182s Capture cancelled as expected 182s ok 182s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:4180): libfprint-virtual_image-DEBUG: 20:26:29.963: 149759054: ../libfprint/drivers/virtual-image.c:216 182s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:29.963: 149759072: ../libfprint/drivers/virtual-device-listener.c:153 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.063: Image device open completed 182s (process:4180): libfprint-device-DEBUG: 20:26:30.063: Device reported open completion 182s (process:4180): libfprint-device-DEBUG: 20:26:30.063: Completing action FPI_DEVICE_ACTION_OPEN in idle! 182s (process:4180): libfprint-device-DEBUG: 20:26:30.063: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4180): libfprint-device-DEBUG: 20:26:30.064: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.064: Activating image device 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.064: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.064: Image device activation completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.064: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.064: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 182s (process:4180): libfprint-device-DEBUG: 20:26:30.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:30.065: Got a new connection! 182s (process:4180): libfprint-virtual_image-DEBUG: 20:26:30.065: image data: 0x3008b760 182s (process:4180): libfprint-device-DEBUG: 20:26:30.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.065: Image device reported finger status: on 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.065: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.065: Image device captured an image 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.065: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 182s (process:4180): libfprint-device-DEBUG: 20:26:30.066: Device reported finger status change: FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-device-DEBUG: 20:26:30.066: Device reported finger status change: FP_FINGER_STATUS_NONE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.066: Image device reported finger status: off 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.066: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image-DEBUG: 20:26:30.091: Minutiae scan completed in 0.026244 secs 182s (process:4180): libfprint-device-DEBUG: 20:26:30.093: Device reported enroll progress, reported 1 of 5 have been completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.093: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 182s (process:4180): libfprint-device-DEBUG: 20:26:30.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:4180): libfprint-device-DEBUG: 20:26:30.093: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.093: Image device reported finger status: on 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.093: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 182s (process:4180): libfprint-virtual_image-DEBUG: 20:26:30.093: image data: 0x3008b760 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.093: Image device captured an image 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.093: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 182s (process:4180): libfprint-device-DEBUG: 20:26:30.093: Device reported finger status change: FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-image-DEBUG: 20:26:30.111: Minutiae scan completed in 0.017735 secs 182s (process:4180): libfprint-device-DEBUG: 20:26:30.111: Device reported enroll progress, reported 2 of 5 have been completed 182s (process:4180): libfprint-device-DEBUG: 20:26:30.111: Device reported finger status change: FP_FINGER_STATUS_NONE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device reported finger status: off 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 182s (process:4180): libfprint-device-DEBUG: 20:26:30.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:4180): libfprint-virtual_image-DEBUG: 20:26:30.111: image data: 0x3008b760 182s (process:4180): libfprint-device-DEBUG: 20:26:30.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device reported finger status: on 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device captured an image 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 182s (process:4180): libfprint-device-DEBUG: 20:26:30.111: Device reported finger status change: FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-device-DEBUG: 20:26:30.111: Device reported finger status change: FP_FINGER_STATUS_NONE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device reported finger status: off 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.111: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image-DEBUG: 20:26:30.129: Minutiae scan completed in 0.017488 secs 182s (process:4180): libfprint-device-DEBUG: 20:26:30.129: Device reported enroll progress, reported 3 of 5 have been completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.129: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 182s (process:4180): libfprint-device-DEBUG: 20:26:30.129: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:4180): libfprint-virtual_image-DEBUG: 20:26:30.130: image data: 0x3008b760 182s (process:4180): libfprint-device-DEBUG: 20:26:30.130: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.130: Image device reported finger status: on 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.130: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.130: Image device captured an image 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.130: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 182s (process:4180): libfprint-device-DEBUG: 20:26:30.132: Device reported finger status change: FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-device-DEBUG: 20:26:30.132: Device reported finger status change: FP_FINGER_STATUS_NONE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.132: Image device reported finger status: off 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.132: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image-DEBUG: 20:26:30.147: Minutiae scan completed in 0.016804 secs 182s (process:4180): libfprint-device-DEBUG: 20:26:30.148: Device reported enroll progress, reported 4 of 5 have been completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 182s (process:4180): libfprint-device-DEBUG: 20:26:30.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:4180): libfprint-virtual_image-DEBUG: 20:26:30.148: image data: 0x3008b760 182s (process:4180): libfprint-device-DEBUG: 20:26:30.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.148: Image device reported finger status: on 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.148: Image device captured an image 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 182s (process:4180): libfprint-device-DEBUG: 20:26:30.148: Device reported finger status change: FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-device-DEBUG: 20:26:30.148: Device reported finger status change: FP_FINGER_STATUS_NONE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.148: Image device reported finger status: off 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.148: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image-DEBUG: 20:26:30.166: Minutiae scan completed in 0.017212 secs 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Device reported enroll progress, reported 5 of 5 have been completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Deactivating image device 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device deactivation completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Device reported enroll completion 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Print for finger FP_FINGER_LEFT_THUMB enrolled 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Activating image device 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device activation completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED 182s (process:4180): libfprint-virtual_image-DEBUG: 20:26:30.166: image data: 0x30099ff0 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device reported finger status: on 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device captured an image 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Device reported finger status change: FP_FINGER_STATUS_PRESENT 182s (process:4180): libfprint-device-DEBUG: 20:26:30.166: Device reported finger status change: FP_FINGER_STATUS_NONE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device reported finger status: off 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.166: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.167: Deactivating image device 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.167: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.167: Image device deactivation completed 182s (process:4180): libfprint-image_device-DEBUG: 20:26:30.167: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 182s (process:4180): libfprint-image-DEBUG: 20:26:30.183: Minutiae scan completed in 0.016150 secs 183s (process:4180): libfprint-print-DEBUG: 20:26:30.994: score 1093/40 183s (process:4180): libfprint-device-DEBUG: 20:26:30.994: Device reported verify result 183s (process:4180): libfprint-device-DEBUG: 20:26:30.994: Device reported verify completion 183s (process:4180): libfprint-device-DEBUG: 20:26:30.994: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 183s (process:4180): libfprint-device-DEBUG: 20:26:30.994: Updated temperature model after 0.83 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:4180): libfprint-device-DEBUG: 20:26:30.996: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.996: Activating image device 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.996: Image device activation completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.996: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 183s (process:4180): libfprint-device-DEBUG: 20:26:30.996: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:4180): libfprint-virtual_image-DEBUG: 20:26:30.997: image data: 0x300a97d0 183s (process:4180): libfprint-device-DEBUG: 20:26:30.997: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device reported finger status: on 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device captured an image 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:4180): libfprint-device-DEBUG: 20:26:30.997: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-device-DEBUG: 20:26:30.997: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device reported finger status: off 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Deactivating image device 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device deactivation completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:30.997: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 183s (process:4180): libfprint-image-DEBUG: 20:26:31.012: Minutiae scan completed in 0.014906 secs 183s (process:4180): libfprint-print-DEBUG: 20:26:31.017: score 10/40 183s (process:4180): libfprint-print-DEBUG: 20:26:31.024: score 10/40 183s (process:4180): libfprint-print-DEBUG: 20:26:31.028: score 10/40 183s (process:4180): libfprint-print-DEBUG: 20:26:31.033: score 10/40 183s (process:4180): libfprint-print-DEBUG: 20:26:31.037: score 10/40 183s (process:4180): libfprint-device-DEBUG: 20:26:31.037: Device reported verify result 183s (process:4180): libfprint-device-DEBUG: 20:26:31.037: Device reported verify completion 183s (process:4180): libfprint-device-DEBUG: 20:26:31.037: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 183s (process:4180): libfprint-device-DEBUG: 20:26:31.037: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:4180): libfprint-device-DEBUG: 20:26:31.037: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.037: Activating image device 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.037: Image device activation completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 183s (process:4180): libfprint-device-DEBUG: 20:26:31.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:4180): libfprint-virtual_image-DEBUG: 20:26:31.038: image data: 0x300b87e0 183s (process:4180): libfprint-device-DEBUG: 20:26:31.038: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.038: Image device reported finger status: on 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.038: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.038: Image device captured an image 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.038: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:4180): libfprint-device-DEBUG: 20:26:31.038: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-device-DEBUG: 20:26:31.038: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.038: Image device reported finger status: off 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.038: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image-DEBUG: 20:26:31.053: Minutiae scan completed in 0.015004 secs 183s (process:4180): libfprint-device-DEBUG: 20:26:31.053: Device reported enroll progress, reported 1 of 5 have been completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.053: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 183s (process:4180): libfprint-device-DEBUG: 20:26:31.053: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:4180): libfprint-device-DEBUG: 20:26:31.054: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.054: Image device reported finger status: on 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.054: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:4180): libfprint-virtual_image-DEBUG: 20:26:31.054: image data: 0x300b87e0 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.054: Image device captured an image 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.054: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:4180): libfprint-device-DEBUG: 20:26:31.054: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image-DEBUG: 20:26:31.068: Minutiae scan completed in 0.014455 secs 183s (process:4180): libfprint-device-DEBUG: 20:26:31.068: Device reported enroll progress, reported 2 of 5 have been completed 183s (process:4180): libfprint-device-DEBUG: 20:26:31.069: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device reported finger status: off 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 183s (process:4180): libfprint-device-DEBUG: 20:26:31.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:4180): libfprint-virtual_image-DEBUG: 20:26:31.069: image data: 0x300b87e0 183s (process:4180): libfprint-device-DEBUG: 20:26:31.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device reported finger status: on 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device captured an image 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:4180): libfprint-device-DEBUG: 20:26:31.069: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-device-DEBUG: 20:26:31.069: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device reported finger status: off 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image-DEBUG: 20:26:31.083: Minutiae scan completed in 0.014419 secs 183s (process:4180): libfprint-device-DEBUG: 20:26:31.084: Device reported enroll progress, reported 3 of 5 have been completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.084: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 183s (process:4180): libfprint-device-DEBUG: 20:26:31.084: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:4180): libfprint-virtual_image-DEBUG: 20:26:31.084: image data: 0x300b87e0 183s (process:4180): libfprint-device-DEBUG: 20:26:31.084: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.084: Image device reported finger status: on 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.084: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.084: Image device captured an image 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.084: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:4180): libfprint-device-DEBUG: 20:26:31.085: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-device-DEBUG: 20:26:31.085: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.085: Image device reported finger status: off 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.085: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image-DEBUG: 20:26:31.099: Minutiae scan completed in 0.014583 secs 183s (process:4180): libfprint-device-DEBUG: 20:26:31.099: Device reported enroll progress, reported 4 of 5 have been completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 183s (process:4180): libfprint-device-DEBUG: 20:26:31.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:4180): libfprint-virtual_image-DEBUG: 20:26:31.099: image data: 0x300b87e0 183s (process:4180): libfprint-device-DEBUG: 20:26:31.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.099: Image device reported finger status: on 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.099: Image device captured an image 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:4180): libfprint-device-DEBUG: 20:26:31.099: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-device-DEBUG: 20:26:31.099: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.099: Image device reported finger status: off 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image-DEBUG: 20:26:31.113: Minutiae scan completed in 0.014314 secs 183s (process:4180): libfprint-device-DEBUG: 20:26:31.113: Device reported enroll progress, reported 5 of 5 have been completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Deactivating image device 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device deactivation completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Device reported enroll completion 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Print for finger FP_FINGER_LEFT_THUMB enrolled 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Activating image device 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device activation completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 183s (process:4180): libfprint-virtual_image-DEBUG: 20:26:31.114: image data: 0x30099ff0 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device reported finger status: on 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device captured an image 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Device reported finger status change: FP_FINGER_STATUS_PRESENT 183s (process:4180): libfprint-device-DEBUG: 20:26:31.114: Device reported finger status change: FP_FINGER_STATUS_NONE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device reported finger status: off 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Deactivating image device 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device deactivation completed 183s (process:4180): libfprint-image_device-DEBUG: 20:26:31.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 183s (process:4180): libfprint-image-DEBUG: 20:26:31.130: Minutiae scan completed in 0.016173 secs 184s (process:4180): libfprint-print-DEBUG: 20:26:31.977: score 1093/40 184s (process:4180): libfprint-device-DEBUG: 20:26:31.977: Device reported verify result 184s (process:4180): libfprint-device-DEBUG: 20:26:31.977: Device reported verify completion 184s (process:4180): libfprint-device-DEBUG: 20:26:31.977: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:31.977: Updated temperature model after 0.86 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-device-DEBUG: 20:26:31.977: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Activating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device activation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:31.978: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:31.978: image data: 0x300a97d0 184s (process:4180): libfprint-device-DEBUG: 20:26:31.978: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:31.978: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:31.978: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Deactivating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device deactivation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:31.978: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 184s (process:4180): libfprint-image-DEBUG: 20:26:31.994: Minutiae scan completed in 0.016164 secs 184s (process:4180): libfprint-print-DEBUG: 20:26:32.000: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.004: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.009: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.014: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.019: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.185: score 855/40 184s (process:4180): libfprint-device-DEBUG: 20:26:32.185: Device reported verify result 184s (process:4180): libfprint-device-DEBUG: 20:26:32.185: Device reported verify completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.185: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.185: Updated temperature model after 0.21 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-device-DEBUG: 20:26:32.185: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.185: Activating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.185: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.185: Image device activation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.185: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.185: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.185: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Device reported verify result 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Deactivating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device deactivation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Device reported verify completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Activating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device activation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Deactivating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device deactivation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Device reported verify completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.186: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.186: 151982074: ../libfprint/drivers/virtual-image.c:244 184s Executing: libfprint-2/virtual-image.test 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.286: Image device close completed 184s (process:4180): libfprint-device-DEBUG: 20:26:32.286: Device reported close completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.286: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.286: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s Print was processed, continuing 184s Print was processed, continuing 184s Print was processed, continuing 184s Print was processed, continuing 184s Print was processed, continuing 184s Enroll done 184s Print was processed, continuing 184s Print was processed, continuing 184s Print was processed, continuing 184s Print was processed, continuing 184s Print was processed, continuing 184s Enroll done 184s fp - device - error - quark: An unspecified error occurred! (0) 184s ok 184s test_features (__main__.VirtualImage.test_features) ... (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.286: 152082465: ../libfprint/drivers/virtual-image.c:216 184s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:32.286: 152082493: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.386: Image device open completed 184s (process:4180): libfprint-device-DEBUG: 20:26:32.386: Device reported open completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.386: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.386: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.387: 152182800: ../libfprint/drivers/virtual-image.c:244 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.487: Image device close completed 184s (process:4180): libfprint-device-DEBUG: 20:26:32.487: Device reported close completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.487: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.487: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s ok 184s test_identify (__main__.VirtualImage.test_identify) ... (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.487: 152282939: ../libfprint/drivers/virtual-image.c:216 184s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:32.487: 152282967: ../libfprint/drivers/virtual-device-listener.c:153 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.587: Image device open completed 184s (process:4180): libfprint-device-DEBUG: 20:26:32.587: Device reported open completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.587: Completing action FPI_DEVICE_ACTION_OPEN in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.587: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-device-DEBUG: 20:26:32.587: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.587: Activating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.587: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.587: Image device activation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.587: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.587: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.587: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:32.587: Got a new connection! 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.588: image data: 0x30099ff0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.588: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.588: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.588: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.588: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.588: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.588: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.588: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.588: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.588: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.607: Minutiae scan completed in 0.018787 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.607: Device reported enroll progress, reported 1 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-device-DEBUG: 20:26:32.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.607: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.607: image data: 0x30099ff0 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.607: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.607: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.607: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image-DEBUG: 20:26:32.624: Minutiae scan completed in 0.016445 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.624: Device reported enroll progress, reported 2 of 5 have been completed 184s (process:4180): libfprint-device-DEBUG: 20:26:32.624: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.624: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.624: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.624: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.624: image data: 0x30099ff0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.624: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.624: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.624: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.624: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.625: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.625: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.625: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.625: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.641: Minutiae scan completed in 0.016913 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.642: Device reported enroll progress, reported 3 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.642: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.642: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.642: image data: 0x30099ff0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.642: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.642: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.642: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.642: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.642: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.642: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.642: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.642: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.642: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.659: Minutiae scan completed in 0.016946 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.659: Device reported enroll progress, reported 4 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.659: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.659: image data: 0x30099ff0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.659: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.659: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.659: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.659: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.661: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.661: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.661: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.661: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.677: Minutiae scan completed in 0.017379 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Device reported enroll progress, reported 5 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Deactivating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device deactivation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Device reported enroll completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Print for finger FP_FINGER_LEFT_THUMB enrolled 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Updated temperature model after 0.09 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Activating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device activation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.677: image data: 0x300c68c0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.677: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.678: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.678: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.678: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.678: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.678: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.694: Minutiae scan completed in 0.016503 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.694: Device reported enroll progress, reported 1 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-device-DEBUG: 20:26:32.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.694: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.694: image data: 0x300a97d0 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.695: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.695: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.695: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image-DEBUG: 20:26:32.712: Minutiae scan completed in 0.017224 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.712: Device reported enroll progress, reported 2 of 5 have been completed 184s (process:4180): libfprint-device-DEBUG: 20:26:32.712: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.712: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.712: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.712: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.712: image data: 0x300a97d0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.712: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.712: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.712: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.713: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.715: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.715: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.715: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.729: Minutiae scan completed in 0.016936 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.730: Device reported enroll progress, reported 3 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.730: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.730: image data: 0x300b87e0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.730: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.730: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.730: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.730: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.730: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.730: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.730: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.730: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.746: Minutiae scan completed in 0.016318 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.746: Device reported enroll progress, reported 4 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.747: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.747: image data: 0x300a97d0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.747: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.747: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.747: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.747: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.747: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.747: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.747: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.764: Minutiae scan completed in 0.016648 secs 184s (process:4180): libfprint-device-DEBUG: 20:26:32.764: Device reported enroll progress, reported 5 of 5 have been completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.764: Deactivating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.764: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.764: Image device deactivation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.764: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 184s (process:4180): libfprint-device-DEBUG: 20:26:32.764: Device reported enroll completion 184s (process:4180): libfprint-device-DEBUG: 20:26:32.764: Print for finger FP_FINGER_LEFT_THUMB enrolled 184s (process:4180): libfprint-device-DEBUG: 20:26:32.764: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 184s (process:4180): libfprint-device-DEBUG: 20:26:32.764: Updated temperature model after 0.09 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-device-DEBUG: 20:26:32.764: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.764: Activating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.764: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.764: Image device activation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.765: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.765: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 184s (process:4180): libfprint-device-DEBUG: 20:26:32.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 184s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.765: image data: 0x300a97d0 184s (process:4180): libfprint-device-DEBUG: 20:26:32.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.765: Image device reported finger status: on 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.765: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.765: Image device captured an image 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.765: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 184s (process:4180): libfprint-device-DEBUG: 20:26:32.767: Device reported finger status change: FP_FINGER_STATUS_PRESENT 184s (process:4180): libfprint-device-DEBUG: 20:26:32.767: Device reported finger status change: FP_FINGER_STATUS_NONE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.767: Image device reported finger status: off 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.767: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.767: Deactivating image device 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.767: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.767: Image device deactivation completed 184s (process:4180): libfprint-image_device-DEBUG: 20:26:32.767: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 184s (process:4180): libfprint-image-DEBUG: 20:26:32.780: Minutiae scan completed in 0.015129 secs 184s (process:4180): libfprint-print-DEBUG: 20:26:32.785: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.789: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.794: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.798: score 10/40 184s (process:4180): libfprint-print-DEBUG: 20:26:32.803: score 10/40 185s (process:4180): libfprint-print-DEBUG: 20:26:32.967: score 855/40 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Device reported identify result 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Device reported identify completion 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Updated temperature model after 0.20 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Activating image device 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device activation completed 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4180): libfprint-virtual_image-DEBUG: 20:26:32.968: image data: 0x300a8870 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device reported finger status: on 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device captured an image 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Device reported finger status change: FP_FINGER_STATUS_PRESENT 185s (process:4180): libfprint-device-DEBUG: 20:26:32.968: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device reported finger status: off 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.968: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.969: Deactivating image device 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.969: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.969: Image device deactivation completed 185s (process:4180): libfprint-image_device-DEBUG: 20:26:32.969: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 185s (process:4180): libfprint-image-DEBUG: 20:26:32.985: Minutiae scan completed in 0.016641 secs 185s (process:4180): libfprint-print-DEBUG: 20:26:33.771: score 1093/40 185s (process:4180): libfprint-device-DEBUG: 20:26:33.771: Device reported identify result 185s (process:4180): libfprint-device-DEBUG: 20:26:33.771: Device reported identify completion 185s (process:4180): libfprint-device-DEBUG: 20:26:33.771: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 185s (process:4180): libfprint-device-DEBUG: 20:26:33.771: Updated temperature model after 0.80 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:4180): libfprint-device-DEBUG: 20:26:33.771: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.771: Activating image device 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.771: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.771: Image device activation completed 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.771: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.771: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 185s (process:4180): libfprint-device-DEBUG: 20:26:33.771: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Device reported identify result 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Deactivating image device 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device deactivation completed 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Device reported identify completion 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Activating image device 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device activation completed 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Deactivating image device 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device deactivation completed 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.772: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Device reported identify completion 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Device reported finger status change: FP_FINGER_STATUS_NONE 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 185s (process:4180): libfprint-device-DEBUG: 20:26:33.772: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s (process:4180): libfprint-virtual_image-DEBUG: 20:26:33.772: 153568493: ../libfprint/drivers/virtual-image.c:244 185s (process:4180): libfprint-image_device-DEBUG: 20:26:33.873: Image device close completed 185s (process:4180): libfprint-device-DEBUG: 20:26:33.873: Device reported close completion 185s (process:4180): libfprint-device-DEBUG: 20:26:33.873: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 185s (process:4180): libfprint-device-DEBUG: 20:26:33.873: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 185s Print was processed, continuing 185s Print was processed, continuing 185s Print was processed, continuing 185s Print was processed, continuing 185s Print was processed, continuing 185s Enroll done 185s Print was processed, continuing 185s Print was processed, continuing 185s Print was processed, continuing 185s Print was processed, continuing 185s Print was processed, continuing 185s Enroll done 185s Identify finished 185s Identify finished 185s Identify finished 185s fp - device - retry - quark: The swipe was too short, please try again. (1) 185s Identify finished 185s fp - device - error - quark: An unspecified error occurred! (0) 185s ok 185s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:4180): libfprint-virtual_image-DEBUG: 20:26:33.873: 153668994: ../libfprint/drivers/virtual-image.c:216 185s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:33.873: 153669060: ../libfprint/drivers/virtual-device-listener.c:153 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.973: Image device open completed 186s (process:4180): libfprint-device-DEBUG: 20:26:33.973: Device reported open completion 186s (process:4180): libfprint-device-DEBUG: 20:26:33.973: Completing action FPI_DEVICE_ACTION_OPEN in idle! 186s (process:4180): libfprint-device-DEBUG: 20:26:33.973: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4180): libfprint-device-DEBUG: 20:26:33.973: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.973: Activating image device 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.973: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.973: Image device activation completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.973: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.973: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 186s (process:4180): libfprint-device-DEBUG: 20:26:33.973: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4180): libfprint-virtual_device_connection-DEBUG: 20:26:33.974: Got a new connection! 186s (process:4180): libfprint-virtual_image-DEBUG: 20:26:33.974: image data: 0x300a8870 186s (process:4180): libfprint-device-DEBUG: 20:26:33.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.974: Image device reported finger status: on 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.974: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.974: Image device captured an image 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.976: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 186s (process:4180): libfprint-device-DEBUG: 20:26:33.976: Device reported finger status change: FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-device-DEBUG: 20:26:33.976: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.976: Image device reported finger status: off 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.976: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image-DEBUG: 20:26:33.991: Minutiae scan completed in 0.016674 secs 186s (process:4180): libfprint-device-DEBUG: 20:26:33.991: Device reported enroll progress, reported 1 of 5 have been completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.991: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 186s (process:4180): libfprint-device-DEBUG: 20:26:33.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4180): libfprint-device-DEBUG: 20:26:33.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.991: Image device reported finger status: on 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.991: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:4180): libfprint-virtual_image-DEBUG: 20:26:33.991: image data: 0x300b70d0 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.991: Image device captured an image 186s (process:4180): libfprint-image_device-DEBUG: 20:26:33.991: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 186s (process:4180): libfprint-device-DEBUG: 20:26:33.991: Device reported finger status change: FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image-DEBUG: 20:26:34.015: Minutiae scan completed in 0.024013 secs 186s (process:4180): libfprint-device-DEBUG: 20:26:34.015: Device reported enroll progress, reported 2 of 5 have been completed 186s (process:4180): libfprint-device-DEBUG: 20:26:34.015: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.016: Image device reported finger status: off 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.016: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.016: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 186s (process:4180): libfprint-device-DEBUG: 20:26:34.016: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4180): libfprint-virtual_image-DEBUG: 20:26:34.016: image data: 0x300a8870 186s (process:4180): libfprint-device-DEBUG: 20:26:34.016: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.016: Image device reported finger status: on 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.016: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.016: Image device captured an image 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.016: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 186s (process:4180): libfprint-device-DEBUG: 20:26:34.018: Device reported finger status change: FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-device-DEBUG: 20:26:34.018: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.018: Image device reported finger status: off 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.018: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image-DEBUG: 20:26:34.033: Minutiae scan completed in 0.016918 secs 186s (process:4180): libfprint-device-DEBUG: 20:26:34.033: Device reported enroll progress, reported 3 of 5 have been completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 186s (process:4180): libfprint-device-DEBUG: 20:26:34.033: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4180): libfprint-virtual_image-DEBUG: 20:26:34.033: image data: 0x300b70d0 186s (process:4180): libfprint-device-DEBUG: 20:26:34.033: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.033: Image device reported finger status: on 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.033: Image device captured an image 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 186s (process:4180): libfprint-device-DEBUG: 20:26:34.033: Device reported finger status change: FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-device-DEBUG: 20:26:34.033: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.033: Image device reported finger status: off 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.033: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image-DEBUG: 20:26:34.051: Minutiae scan completed in 0.017480 secs 186s (process:4180): libfprint-device-DEBUG: 20:26:34.051: Device reported enroll progress, reported 4 of 5 have been completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.051: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 186s (process:4180): libfprint-device-DEBUG: 20:26:34.051: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4180): libfprint-virtual_image-DEBUG: 20:26:34.051: image data: 0x300a8870 186s (process:4180): libfprint-device-DEBUG: 20:26:34.051: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.051: Image device reported finger status: on 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.051: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.051: Image device captured an image 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.051: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 186s (process:4180): libfprint-device-DEBUG: 20:26:34.053: Device reported finger status change: FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-device-DEBUG: 20:26:34.053: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.053: Image device reported finger status: off 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.053: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image-DEBUG: 20:26:34.068: Minutiae scan completed in 0.016934 secs 186s (process:4180): libfprint-device-DEBUG: 20:26:34.068: Device reported enroll progress, reported 5 of 5 have been completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.068: Deactivating image device 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.068: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.068: Image device deactivation completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.068: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 186s (process:4180): libfprint-device-DEBUG: 20:26:34.068: Device reported enroll completion 186s (process:4180): libfprint-device-DEBUG: 20:26:34.068: Print for finger FP_FINGER_LEFT_THUMB enrolled 186s (process:4180): libfprint-device-DEBUG: 20:26:34.068: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 186s (process:4180): libfprint-device-DEBUG: 20:26:34.068: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4180): libfprint-device-DEBUG: 20:26:34.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Activating image device 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device activation completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 186s (process:4180): libfprint-device-DEBUG: 20:26:34.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4180): libfprint-virtual_image-DEBUG: 20:26:34.069: image data: 0x300a8870 186s (process:4180): libfprint-device-DEBUG: 20:26:34.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device reported finger status: on 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device captured an image 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 186s (process:4180): libfprint-device-DEBUG: 20:26:34.069: Device reported finger status change: FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-device-DEBUG: 20:26:34.069: Device reported finger status change: FP_FINGER_STATUS_NONE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device reported finger status: off 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Deactivating image device 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device deactivation completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.069: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 186s (process:4180): libfprint-image-DEBUG: 20:26:34.086: Minutiae scan completed in 0.016738 secs 186s (process:4180): libfprint-print-DEBUG: 20:26:34.909: score 1093/40 186s (process:4180): libfprint-device-DEBUG: 20:26:34.909: Device reported verify result 186s (process:4180): libfprint-device-DEBUG: 20:26:34.909: Device reported verify completion 186s (process:4180): libfprint-device-DEBUG: 20:26:34.909: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 186s (process:4180): libfprint-device-DEBUG: 20:26:34.909: Updated temperature model after 0.84 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4180): libfprint-device-DEBUG: 20:26:34.909: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.909: Activating image device 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.910: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.910: Image device activation completed 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.910: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.910: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 186s (process:4180): libfprint-device-DEBUG: 20:26:34.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 186s (process:4180): libfprint-virtual_image-DEBUG: 20:26:34.910: image data: 0x300a97d0 186s (process:4180): libfprint-device-DEBUG: 20:26:34.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.910: Image device reported finger status: on 186s (process:4180): libfprint-image_device-DEBUG: 20:26:34.910: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.910: Image device captured an image 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 187s (process:4180): libfprint-device-DEBUG: 20:26:34.912: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:4180): libfprint-device-DEBUG: 20:26:34.912: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.912: Image device reported finger status: off 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.912: Deactivating image device 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.912: Image device deactivation completed 187s (process:4180): libfprint-image_device-DEBUG: 20:26:34.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 187s (process:4180): libfprint-image-DEBUG: 20:26:34.925: Minutiae scan completed in 0.014710 secs 187s (process:4180): libfprint-print-DEBUG: 20:26:34.929: score 10/40 187s (process:4180): libfprint-print-DEBUG: 20:26:34.934: score 10/40 187s (process:4180): libfprint-print-DEBUG: 20:26:34.939: score 10/40 187s (process:4180): libfprint-print-DEBUG: 20:26:34.943: score 10/40 187s (process:4180): libfprint-print-DEBUG: 20:26:34.948: score 10/40 187s (process:4180): libfprint-device-DEBUG: 20:26:34.948: Device reported verify result 187s (process:4180): libfprint-device-DEBUG: 20:26:34.948: Device reported verify completion 187s (process:4180): libfprint-device-DEBUG: 20:26:34.948: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 187s (process:4180): libfprint-device-DEBUG: 20:26:34.948: Updated temperature model after 0.04 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:4180): libfprint-virtual_image-DEBUG: 20:26:34.948: 154743891: ../libfprint/drivers/virtual-image.c:244 187s (process:4180): libfprint-image_device-DEBUG: 20:26:35.048: Image device close completed 187s (process:4180): libfprint-device-DEBUG: 20:26:35.048: Device reported close completion 187s (process:4180): libfprint-device-DEBUG: 20:26:35.048: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:4180): libfprint-device-DEBUG: 20:26:35.048: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s Print was processed, continuing 187s Print was processed, continuing 187s Print was processed, continuing 187s Print was processed, continuing 187s Print was processed, continuing 187s Enroll done 187s ok 187s 187s ---------------------------------------------------------------------- 187s Ran 5 tests in 5.297s 187s 187s OK 187s PASS: libfprint-2/virtual-image.test 187s Running test: libfprint-2/driver-nb1010.test 187s ** (umockdev-run:4190): DEBUG: 20:26:35.100: umockdev.vala:127: Created udev test bed /tmp/umockdev.7HP112 187s ** (umockdev-run:4190): DEBUG: 20:26:35.101: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 187s ** (umockdev-run:4190): DEBUG: 20:26:35.104: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 187s ** (umockdev-run:4190): DEBUG: 20:26:35.107: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7HP112/dev/bus/usb/001/003 187s ** (umockdev-run:4190): DEBUG: 20:26:35.107: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 187s ** (umockdev-run:4190): DEBUG: 20:26:35.110: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 187s ** (umockdev-run:4190): DEBUG: 20:26:35.113: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7HP112/dev/bus/usb/001/001 187s ** (umockdev-run:4190): DEBUG: 20:26:35.113: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 187s ** (umockdev-run:4190): DEBUG: 20:26:35.114: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 187s ** (umockdev-run:4190): DEBUG: 20:26:35.117: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3 187s ** (umockdev-run:4190): DEBUG: 20:26:35.118: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 187s (umockdev-run:4190): GLib-GIO-DEBUG: 20:26:35.121: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 187s (process:4194): libfprint-context-DEBUG: 20:26:35.194: Initializing FpContext (libfprint version 1.94.8+tod1) 187s (process:4194): libfprint-tod-DEBUG: 20:26:35.194: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:4194): libfprint-context-DEBUG: 20:26:35.196: No driver found for USB device 1D6B:0002 187s (process:4194): libfprint-device-DEBUG: 20:26:35.196: Device reported probe completion 187s (process:4194): libfprint-device-DEBUG: 20:26:35.196: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:4194): libfprint-device-DEBUG: 20:26:35.196: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.198: Image device open completed 187s (process:4194): libfprint-device-DEBUG: 20:26:35.198: Device reported open completion 187s (process:4194): libfprint-nb1010-DEBUG: 20:26:35.198: nb1010 Initialized 187s (process:4194): libfprint-device-DEBUG: 20:26:35.198: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s (process:4194): libfprint-device-DEBUG: 20:26:35.198: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:4194): libfprint-device-DEBUG: 20:26:35.198: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.198: Activating image device 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.198: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.198: Image device activation completed 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.198: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.198: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.198: [nb1010] M_LOOP_NUM_STATES entering state 0 187s (process:4194): libfprint-device-DEBUG: 20:26:35.198: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:4194): libfprint-nb1010-DEBUG: 20:26:35.198: nb1010 Activated 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.248: [nb1010] M_LOOP_NUM_STATES entering state 1 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.248: [nb1010] M_LOOP_NUM_STATES entering state 2 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.249: [nb1010] M_LOOP_NUM_STATES entering state 3 187s (process:4194): libfprint-device-DEBUG: 20:26:35.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.249: Image device reported finger status: on 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.249: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.250: [nb1010] M_LOOP_NUM_STATES entering state 4 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.251: [nb1010] M_LOOP_NUM_STATES entering state 5 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.288: [nb1010] M_LOOP_NUM_STATES entering state 6 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.288: Image device captured an image 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.289: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 187s (process:4194): libfprint-device-DEBUG: 20:26:35.289: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:4194): libfprint-SSM-DEBUG: 20:26:35.289: [nb1010] M_LOOP_NUM_STATES completed successfully 187s (process:4194): libfprint-nb1010-DEBUG: 20:26:35.289: nb1010 ssm complete cb 187s (process:4194): libfprint-device-DEBUG: 20:26:35.289: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.289: Image device reported finger status: off 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.289: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.289: Deactivating image device 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.289: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.289: Image device deactivation completed 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.289: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 187s (process:4194): libfprint-nb1010-DEBUG: 20:26:35.289: nb1010 Deactivated 187s (process:4194): libfprint-device-DEBUG: 20:26:35.298: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 187s (process:4194): libfprint-image-DEBUG: 20:26:35.301: Minutiae scan completed in 0.012130 secs 187s (process:4194): libfprint-device-DEBUG: 20:26:35.301: Device reported capture completion 187s (process:4194): libfprint-device-DEBUG: 20:26:35.301: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 187s (process:4194): libfprint-device-DEBUG: 20:26:35.301: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:4194): libfprint-image_device-DEBUG: 20:26:35.302: Image device close completed 187s (process:4194): libfprint-device-DEBUG: 20:26:35.302: Device reported close completion 187s (process:4194): libfprint-nb1010-DEBUG: 20:26:35.302: nb1010 Deinitialized 187s (process:4194): libfprint-device-DEBUG: 20:26:35.302: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:4194): libfprint-device-DEBUG: 20:26:35.302: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s ** (umockdev-run:4190): DEBUG: 20:26:35.360: umockdev.vala:154: Removing test bed /tmp/umockdev.7HP112 187s (umockdev-run:4190): GLib-DEBUG: 20:26:35.367: unsetenv() is not thread-safe and should not be used after threads are created 187s Comparing PNGs /tmp/libfprint-umockdev-test-iju99yrs/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 187s PASS: libfprint-2/driver-nb1010.test 187s Running test: libfprint-2/driver-egis0570.test 187s ** (umockdev-run:4203): DEBUG: 20:26:35.418: umockdev.vala:127: Created udev test bed /tmp/umockdev.9LY812 187s ** (umockdev-run:4203): DEBUG: 20:26:35.419: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 187s ** (umockdev-run:4203): DEBUG: 20:26:35.420: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 187s ** (umockdev-run:4203): DEBUG: 20:26:35.423: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9LY812/dev/bus/usb/001/005 187s ** (umockdev-run:4203): DEBUG: 20:26:35.423: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 187s ** (umockdev-run:4203): DEBUG: 20:26:35.424: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 187s ** (umockdev-run:4203): DEBUG: 20:26:35.427: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9LY812/dev/bus/usb/001/001 187s ** (umockdev-run:4203): DEBUG: 20:26:35.427: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 187s ** (umockdev-run:4203): DEBUG: 20:26:35.427: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 187s (process:4207): libfprint-context-DEBUG: 20:26:35.501: Initializing FpContext (libfprint version 1.94.8+tod1) 187s (process:4207): libfprint-tod-DEBUG: 20:26:35.501: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 187s (process:4207): libfprint-context-DEBUG: 20:26:35.503: No driver found for USB device 1D6B:0002 187s (process:4207): libfprint-device-DEBUG: 20:26:35.503: Device reported probe completion 187s (process:4207): libfprint-device-DEBUG: 20:26:35.503: Completing action FPI_DEVICE_ACTION_PROBE in idle! 187s (process:4207): libfprint-device-DEBUG: 20:26:35.503: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.504: Image device open completed 187s (process:4207): libfprint-device-DEBUG: 20:26:35.504: Device reported open completion 187s (process:4207): libfprint-device-DEBUG: 20:26:35.504: Completing action FPI_DEVICE_ACTION_OPEN in idle! 187s (process:4207): libfprint-device-DEBUG: 20:26:35.504: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:4207): libfprint-device-DEBUG: 20:26:35.504: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.504: Activating image device 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.504: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.504: [egis0570] SM_STATES_NUM entering state 0 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.504: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.504: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.505: Image device activation completed 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 187s (process:4207): libfprint-device-DEBUG: 20:26:35.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.505: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.505: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.506: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.506: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.507: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.507: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.508: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.508: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.509: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.509: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.510: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.510: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.510: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.511: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.511: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.512: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.512: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.512: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.513: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.513: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.514: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.514: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.515: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.515: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.516: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.516: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.517: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.517: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.517: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.518: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.518: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.518: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.519: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.519: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.520: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.520: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.521: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.521: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.521: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.522: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.522: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.523: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.523: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.523: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.524: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.524: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.525: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.525: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.525: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.525: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.525: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.525: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.526: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.526: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.527: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.527: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.528: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.528: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.528: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.528: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.528: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.528: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.528: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.528: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.528: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.528: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.528: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.529: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.529: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.530: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.530: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.531: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.531: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.532: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.532: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.532: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.532: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.532: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.532: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.532: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.532: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.532: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.532: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.532: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.533: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.533: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.533: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.534: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.534: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.534: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.535: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.535: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.536: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.536: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.536: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.536: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.536: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.536: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.536: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.536: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.536: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.536: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.536: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.537: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.537: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.538: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.538: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.538: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.538: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.539: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.539: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.539: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.539: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.539: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.539: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.539: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.539: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.539: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.539: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.540: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.540: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.541: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.541: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.541: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.542: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.542: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.542: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.542: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.542: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.542: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.542: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.542: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.542: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.542: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.542: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.543: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.543: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.544: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.544: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.545: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.545: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.546: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.546: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.546: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.546: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.546: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.546: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.546: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.546: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.546: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.546: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.546: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.547: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.547: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.547: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.548: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.548: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.549: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.549: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.549: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.550: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.550: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.550: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.550: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.550: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.550: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.550: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.550: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.550: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.550: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.550: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.551: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.551: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.552: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.552: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.552: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.552: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.553: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.553: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.553: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.553: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.553: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.553: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.553: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.553: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.553: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.553: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.554: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.554: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.554: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.555: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.555: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.556: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.556: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.556: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.556: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.556: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.556: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.556: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.556: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.556: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.556: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.556: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.557: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.557: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.558: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.558: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.558: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.559: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.559: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.559: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.560: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.560: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.560: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.560: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.560: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.560: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.560: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.560: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.560: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.560: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.560: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.561: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.561: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.562: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.562: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.563: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.563: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.563: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.563: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.563: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.563: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.563: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.563: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.563: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.563: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.563: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.564: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.564: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.564: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.565: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.565: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.565: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.566: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.566: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.566: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.566: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.566: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.566: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.566: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.566: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.566: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.566: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.566: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.567: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.567: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.568: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.568: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.569: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.569: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.569: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.569: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.570: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.570: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.570: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.570: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.570: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.570: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.570: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.570: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.570: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.570: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.571: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.571: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.571: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.572: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.572: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.573: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.573: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.573: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.573: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.573: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.573: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.573: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.573: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.573: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.573: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.573: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.574: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.574: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.575: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.575: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.576: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.576: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.576: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.576: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.577: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.577: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.577: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.577: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.577: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.577: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.577: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.577: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.577: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.577: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.578: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.578: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.578: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.579: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.579: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.580: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.580: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.580: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.580: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.580: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.580: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.580: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.580: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.580: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.580: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.580: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.581: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.581: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.582: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.582: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.583: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.583: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.583: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.583: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.584: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.584: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.584: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.584: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.584: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.584: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.584: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.584: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.584: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.584: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.585: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.585: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.586: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.586: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.586: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.587: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.587: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.588: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.588: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.588: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.588: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.588: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.588: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.588: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.588: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.588: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.588: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.588: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.589: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.589: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.590: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.590: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.591: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.591: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.591: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.591: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.591: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.591: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.591: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.591: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.591: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.591: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.591: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.592: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.592: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.592: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.593: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.593: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.593: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.594: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.594: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.595: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.595: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.595: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.595: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.595: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.595: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.595: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.595: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.595: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.595: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.595: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.596: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.596: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.597: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.597: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.598: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.598: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.598: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.598: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.598: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.598: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.598: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.598: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.598: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.598: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.598: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.599: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.599: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.600: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.600: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.600: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.601: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.601: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.601: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.602: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.602: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.602: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.602: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.602: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.602: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.602: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.602: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.602: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.602: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.602: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.603: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.603: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.604: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.604: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-device-DEBUG: 20:26:35.605: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.605: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.605: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.605: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.605: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.605: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.605: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.605: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.605: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.605: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.605: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.605: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.606: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.606: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.607: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.607: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.607: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.608: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.608: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.608: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.609: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.609: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.609: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.609: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.609: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.609: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.609: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.609: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.609: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.609: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.610: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.610: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.610: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.611: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.611: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.612: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.612: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.612: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.612: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.612: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.612: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.612: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.612: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.612: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.612: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.612: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.613: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.613: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.613: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.614: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.614: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.615: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.615: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.615: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.616: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.616: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.616: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.616: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.616: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.616: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.616: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.616: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.616: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.616: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.616: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.617: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.617: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.618: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.618: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.619: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.619: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.619: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.619: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.619: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.619: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.619: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.619: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.619: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.619: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.619: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.619: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.620: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.620: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.621: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.621: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.621: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.622: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.622: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.622: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.622: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.622: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.622: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.622: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.622: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.622: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.622: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.622: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.623: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.623: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.624: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.624: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.625: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.625: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.626: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.626: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.626: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.626: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.626: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.626: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.626: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.626: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.626: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.626: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.626: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.627: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.627: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.627: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.628: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.628: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.629: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.629: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.629: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.630: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.630: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.630: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.630: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.630: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.630: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.630: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.630: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.630: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.630: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.630: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.631: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.631: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.632: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.632: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.633: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.633: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.633: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.633: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.633: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.633: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.633: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.633: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.633: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.633: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.633: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.633: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.634: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.634: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.635: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.635: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.636: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.636: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.636: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.637: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.637: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.637: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.637: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.637: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.637: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.637: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.637: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.637: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.637: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.637: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.638: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.638: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.639: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.639: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.639: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.640: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.640: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.640: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.640: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.640: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.640: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.640: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.640: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.640: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.640: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.640: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.641: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.641: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.642: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.642: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.642: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.643: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.643: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.643: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.643: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.643: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.643: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.643: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.643: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.643: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.643: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.643: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.644: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.644: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.645: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.645: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.646: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.646: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.646: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.646: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.647: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.647: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.647: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.647: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.647: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.647: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.647: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.647: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.647: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.647: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.648: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.648: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.648: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.649: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.649: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.650: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.650: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.650: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.650: Finger status (picture number, mean) : 1 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.650: Finger status (picture number, mean) : 2 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.650: Finger status (picture number, mean) : 3 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.650: Finger status (picture number, mean) : 4 , 0 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.650: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.650: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.650: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.650: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.651: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.651: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.652: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.652: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.653: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.653: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.654: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.654: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.654: Finger status (picture number, mean) : 0 , 0 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.654: Finger status (picture number, mean) : 1 , 1 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.654: Finger status (picture number, mean) : 2 , 2 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.654: Finger status (picture number, mean) : 3 , 3 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.654: Finger status (picture number, mean) : 4 , 6 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.654: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.654: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.654: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.654: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.654: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.655: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.655: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.656: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.656: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.657: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.657: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.657: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.658: Finger status (picture number, mean) : 0 , 11 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.658: Finger status (picture number, mean) : 1 , 16 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.658: Finger status (picture number, mean) : 2 , 23 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.658: Finger status (picture number, mean) : 3 , 28 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.658: Finger status (picture number, mean) : 4 , 32 187s (process:4207): libfprint-device-DEBUG: 20:26:35.658: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.658: Image device reported finger status: on 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.658: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 187s (process:4207): libfprint-device-DEBUG: 20:26:35.658: Device reported finger status change: FP_FINGER_STATUS_NEEDED 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.658: Image device reported finger status: off 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.658: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.658: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.658: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.658: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.658: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.659: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.659: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.660: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.660: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.661: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.661: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.661: Finger status (picture number, mean) : 0 , 38 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.661: Finger status (picture number, mean) : 1 , 43 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.661: Finger status (picture number, mean) : 2 , 48 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.661: Finger status (picture number, mean) : 3 , 54 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.661: Finger status (picture number, mean) : 4 , 58 187s (process:4207): libfprint-device-DEBUG: 20:26:35.661: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.661: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.661: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.661: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.661: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.662: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.662: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.663: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.663: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.663: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.664: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.664: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.664: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.665: Finger status (picture number, mean) : 0 , 62 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.665: Finger status (picture number, mean) : 1 , 68 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.665: Finger status (picture number, mean) : 2 , 71 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.665: Finger status (picture number, mean) : 3 , 73 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.665: Finger status (picture number, mean) : 4 , 77 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.665: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.665: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.665: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.665: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.665: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.665: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.666: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.666: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.667: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.667: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.668: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.668: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.668: Finger status (picture number, mean) : 0 , 79 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.668: Finger status (picture number, mean) : 1 , 79 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.668: Finger status (picture number, mean) : 2 , 82 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.668: Finger status (picture number, mean) : 3 , 84 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.668: Finger status (picture number, mean) : 4 , 85 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.668: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.668: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.668: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.668: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.669: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.669: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.669: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.670: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.670: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.671: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.671: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.671: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.672: Finger status (picture number, mean) : 0 , 88 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.672: Finger status (picture number, mean) : 1 , 89 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.672: Finger status (picture number, mean) : 2 , 90 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.672: Finger status (picture number, mean) : 3 , 92 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.672: Finger status (picture number, mean) : 4 , 92 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.672: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.672: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.672: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.672: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.672: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.673: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.673: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.673: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.674: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.674: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.675: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.675: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.675: Finger status (picture number, mean) : 0 , 93 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.675: Finger status (picture number, mean) : 1 , 94 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.675: Finger status (picture number, mean) : 2 , 95 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.675: Finger status (picture number, mean) : 3 , 96 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.675: Finger status (picture number, mean) : 4 , 97 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.675: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.675: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.675: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.675: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.676: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.676: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.677: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.677: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.677: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.678: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.678: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.678: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.679: Finger status (picture number, mean) : 0 , 97 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.679: Finger status (picture number, mean) : 1 , 95 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.679: Finger status (picture number, mean) : 2 , 95 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.679: Finger status (picture number, mean) : 3 , 96 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.679: Finger status (picture number, mean) : 4 , 97 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.679: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.679: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.679: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.679: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.679: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.679: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.680: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.680: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.681: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.681: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.682: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.682: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.682: Finger status (picture number, mean) : 0 , 96 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.682: Finger status (picture number, mean) : 1 , 97 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.682: Finger status (picture number, mean) : 2 , 98 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.682: Finger status (picture number, mean) : 3 , 98 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.682: Finger status (picture number, mean) : 4 , 98 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.682: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.682: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.682: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.682: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.683: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.683: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.684: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.684: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.684: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.685: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.685: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.685: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.686: Finger status (picture number, mean) : 0 , 98 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.686: Finger status (picture number, mean) : 1 , 99 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.686: Finger status (picture number, mean) : 2 , 100 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.686: Finger status (picture number, mean) : 3 , 99 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.686: Finger status (picture number, mean) : 4 , 97 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.686: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.686: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.686: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.686: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.686: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.687: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.687: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.688: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.688: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.689: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.689: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.689: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.690: Finger status (picture number, mean) : 0 , 98 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.690: Finger status (picture number, mean) : 1 , 98 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.690: Finger status (picture number, mean) : 2 , 98 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.690: Finger status (picture number, mean) : 3 , 95 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.690: Finger status (picture number, mean) : 4 , 91 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.690: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.690: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.690: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.690: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.690: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.690: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.691: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.691: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.692: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.692: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.693: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.693: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.693: Finger status (picture number, mean) : 0 , 88 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.693: Finger status (picture number, mean) : 1 , 88 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.693: Finger status (picture number, mean) : 2 , 88 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.693: Finger status (picture number, mean) : 3 , 87 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.693: Finger status (picture number, mean) : 4 , 89 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.693: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.693: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.693: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.693: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.694: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.694: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.695: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.695: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.695: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.696: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.696: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.696: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.697: Finger status (picture number, mean) : 0 , 88 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.697: Finger status (picture number, mean) : 1 , 89 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.697: Finger status (picture number, mean) : 2 , 90 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.697: Finger status (picture number, mean) : 3 , 91 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.697: Finger status (picture number, mean) : 4 , 89 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.697: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.697: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.697: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.697: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.697: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.697: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.698: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.698: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.699: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.699: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.700: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.700: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.700: Finger status (picture number, mean) : 0 , 90 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.700: Finger status (picture number, mean) : 1 , 89 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.700: Finger status (picture number, mean) : 2 , 85 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.700: Finger status (picture number, mean) : 3 , 75 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.700: Finger status (picture number, mean) : 4 , 46 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.700: Image device reported finger status: on 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.700: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.700: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.700: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.701: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.701: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.701: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.702: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.702: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.702: [egis0570] SM_STATES_NUM entering state 2 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.703: [egis0570] SM_STATES_NUM entering state 3 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.703: [egis0570] SM_STATES_NUM entering state 4 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.704: Finger status (picture number, mean) : 0 , 17 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.704: Finger status (picture number, mean) : 1 , 14 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.704: Finger status (picture number, mean) : 2 , 15 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.704: Finger status (picture number, mean) : 3 , 15 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.704: Finger status (picture number, mean) : 4 , 15 187s (process:4207): libfprint-assembling-DEBUG: 20:26:35.742: calc delta completed in 0.037960 secs 187s (process:4207): libfprint-assembling-DEBUG: 20:26:35.780: calc delta completed in 0.037869 secs 187s (process:4207): libfprint-assembling-DEBUG: 20:26:35.780: errors: 10243 rev: 29954 187s (process:4207): libfprint-assembling-DEBUG: 20:26:35.819: calc delta completed in 0.038858 secs 187s (process:4207): libfprint-assembling-DEBUG: 20:26:35.819: height is 292 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.821: Image device captured an image 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 187s (process:4207): libfprint-device-DEBUG: 20:26:35.822: Device reported finger status change: FP_FINGER_STATUS_PRESENT 187s (process:4207): libfprint-device-DEBUG: 20:26:35.822: Device reported finger status change: FP_FINGER_STATUS_NONE 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.822: Image device reported finger status: off 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.822: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.822: Deactivating image device 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.822: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.822: [egis0570] SM_STATES_NUM entering state 5 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.822: [egis0570] SM_STATES_NUM entering state 1 187s (process:4207): libfprint-egis0570-DEBUG: 20:26:35.822: deactivating, marking completed 187s (process:4207): libfprint-SSM-DEBUG: 20:26:35.822: [egis0570] SM_STATES_NUM completed successfully 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.822: Image device deactivation completed 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.822: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 187s (process:4207): libfprint-image-DEBUG: 20:26:35.852: Minutiae scan completed in 0.031111 secs 187s (process:4207): libfprint-device-DEBUG: 20:26:35.852: Device reported capture completion 187s (process:4207): libfprint-device-DEBUG: 20:26:35.853: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 187s (process:4207): libfprint-device-DEBUG: 20:26:35.853: Updated temperature model after 0.25 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 187s (process:4207): libfprint-image_device-DEBUG: 20:26:35.853: Image device close completed 187s (process:4207): libfprint-device-DEBUG: 20:26:35.853: Device reported close completion 187s (process:4207): libfprint-device-DEBUG: 20:26:35.853: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 187s (process:4207): libfprint-device-DEBUG: 20:26:35.853: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 188s ** (umockdev-run:4203): DEBUG: 20:26:36.045: umockdev.vala:154: Removing test bed /tmp/umockdev.9LY812 188s (umockdev-run:4203): GLib-DEBUG: 20:26:36.050: unsetenv() is not thread-safe and should not be used after threads are created 188s Comparing PNGs /tmp/libfprint-umockdev-test-45otbzit/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 188s PASS: libfprint-2/driver-egis0570.test 188s Running test: libfprint-2/driver-aes2501.test 188s ** (umockdev-run:4216): DEBUG: 20:26:36.131: umockdev.vala:127: Created udev test bed /tmp/umockdev.7RU312 188s ** (umockdev-run:4216): DEBUG: 20:26:36.131: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 188s ** (umockdev-run:4216): DEBUG: 20:26:36.132: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 188s ** (umockdev-run:4216): DEBUG: 20:26:36.136: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7RU312/dev/bus/usb/001/044 188s ** (umockdev-run:4216): DEBUG: 20:26:36.136: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 188s ** (umockdev-run:4216): DEBUG: 20:26:36.136: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 188s ** (umockdev-run:4216): DEBUG: 20:26:36.139: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7RU312/dev/bus/usb/001/001 188s ** (umockdev-run:4216): DEBUG: 20:26:36.139: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 188s ** (umockdev-run:4216): DEBUG: 20:26:36.140: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 188s (process:4220): libfprint-context-DEBUG: 20:26:36.212: Initializing FpContext (libfprint version 1.94.8+tod1) 188s (process:4220): libfprint-tod-DEBUG: 20:26:36.212: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 188s (process:4220): libfprint-context-DEBUG: 20:26:36.214: No driver found for USB device 1D6B:0002 188s (process:4220): libfprint-device-DEBUG: 20:26:36.214: Device reported probe completion 188s (process:4220): libfprint-device-DEBUG: 20:26:36.214: Completing action FPI_DEVICE_ACTION_PROBE in idle! 188s (process:4220): libfprint-device-DEBUG: 20:26:36.214: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:4220): libfprint-image_device-DEBUG: 20:26:36.216: Image device open completed 188s (process:4220): libfprint-device-DEBUG: 20:26:36.216: Device reported open completion 188s (process:4220): libfprint-device-DEBUG: 20:26:36.216: Completing action FPI_DEVICE_ACTION_OPEN in idle! 188s (process:4220): libfprint-device-DEBUG: 20:26:36.216: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:4220): libfprint-device-DEBUG: 20:26:36.216: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 188s (process:4220): libfprint-image_device-DEBUG: 20:26:36.216: Activating image device 188s (process:4220): libfprint-image_device-DEBUG: 20:26:36.216: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 188s (process:4220): libfprint-SSM-DEBUG: 20:26:36.216: [aes2501] ACTIVATE_NUM_STATES entering state 0 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.216: write 38 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.218: all registers written 188s (process:4220): libfprint-SSM-DEBUG: 20:26:36.218: [aes2501] ACTIVATE_NUM_STATES entering state 1 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.218: read data 1 188s (process:4220): libfprint-SSM-DEBUG: 20:26:36.219: [aes2501] ACTIVATE_NUM_STATES entering state 2 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.219: write 7 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.219: all registers written 188s (process:4220): libfprint-SSM-DEBUG: 20:26:36.219: [aes2501] ACTIVATE_NUM_STATES entering state 3 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.219: 156015335: ../libfprint/drivers/aes2501.c:140 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.219: write 1 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.220: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.220: reg 0xaf = 20 188s (process:4220): libfprint-SSM-DEBUG: 20:26:36.220: [aes2501] ACTIVATE_NUM_STATES entering state 5 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.220: write 7 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.221: all registers written 188s (process:4220): libfprint-SSM-DEBUG: 20:26:36.221: [aes2501] ACTIVATE_NUM_STATES entering state 6 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.221: write 16 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.221: all registers written 188s (process:4220): libfprint-SSM-DEBUG: 20:26:36.222: [aes2501] ACTIVATE_NUM_STATES completed successfully 188s (process:4220): libfprint-image_device-DEBUG: 20:26:36.222: Image device activation completed 188s (process:4220): libfprint-image_device-DEBUG: 20:26:36.222: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 188s (process:4220): libfprint-image_device-DEBUG: 20:26:36.222: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 188s (process:4220): libfprint-device-DEBUG: 20:26:36.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.222: 156017645: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.222: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.223: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.224: 156019734: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.224: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.225: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.226: 156021917: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.226: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.228: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.228: 156024142: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.228: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.229: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.230: 156025880: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.230: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.231: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.232: 156027839: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.232: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.233: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.234: 156029699: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.234: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.235: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.235: 156031466: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.235: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.237: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.238: 156033740: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.238: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.239: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.240: 156036223: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.240: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.241: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.242: 156037870: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.242: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.243: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.243: 156039601: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.244: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.245: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.245: 156041273: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.245: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.246: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.247: 156043049: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.247: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.248: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.249: 156044731: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.249: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.250: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.250: 156046429: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.250: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.252: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.252: 156048157: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.252: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.253: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.254: 156049756: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.254: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.255: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.255: 156051425: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.255: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.257: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.257: 156053071: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.257: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.258: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.259: 156054775: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.259: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.260: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.260: 156056505: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.260: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.262: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.262: 156058143: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.262: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.263: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.264: 156059845: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.264: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.265: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.265: 156061533: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.265: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.267: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.267: 156063179: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.267: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.268: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.269: 156064807: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.269: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.270: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.270: 156066508: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.270: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.272: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.272: 156068198: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.272: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.273: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.274: 156069909: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.274: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.275: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.276: 156071626: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.276: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.277: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.277: 156073278: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.277: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.278: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.279: 156074999: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.279: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.280: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.281: 156076759: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.281: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.282: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.282: 156078449: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.282: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.284: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.284: 156080152: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.284: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.285: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.286: 156081856: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.286: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.287: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.287: 156083582: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.287: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.289: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.289: 156085245: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.289: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.290: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.291: 156086881: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.291: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.292: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.293: 156088699: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.293: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.294: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.294: 156090482: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.294: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.296: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.296: 156092522: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.296: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.298: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.298: 156094289: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.298: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.300: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.300: 156096070: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.300: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.301: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.302: 156097788: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.302: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.303: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.303: 156099538: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.303: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.305: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.305: 156101273: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.305: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.306: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.307: 156102859: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.307: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.308: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.308: 156104592: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.308: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.310: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.310: 156106319: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.310: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.312: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.312: 156108049: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.312: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.313: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.314: 156109777: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.314: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.315: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.315: 156111486: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.315: write 23 regs 188s (process:4220): libfprint-device-DEBUG: 20:26:36.316: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.317: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.317: 156113196: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.317: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.318: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.319: 156114936: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.319: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.320: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.321: 156116647: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.321: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.322: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.322: 156118369: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.322: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.324: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.324: 156120059: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.324: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.325: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.326: 156121810: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.326: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.327: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.327: 156123528: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.327: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.329: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.329: 156125293: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.329: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.330: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.331: 156127064: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.331: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.332: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.333: 156128777: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.333: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.334: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.334: 156130523: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.334: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.336: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.336: 156132231: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.336: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.337: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.338: 156133915: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.338: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.339: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.340: 156135644: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.340: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.341: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.342: 156137859: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.342: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.343: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.344: 156139608: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.344: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.345: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.345: 156141299: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.345: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.346: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.347: 156143014: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.347: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.348: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.349: 156144772: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.349: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.350: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.350: 156146538: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.350: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.352: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.352: 156148269: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.352: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.353: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.354: 156150013: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.354: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.355: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.356: 156151770: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.356: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.357: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.357: 156153523: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.357: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.359: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.359: 156155191: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.359: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.360: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.361: 156156857: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.361: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.362: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.363: 156158619: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.363: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.364: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.364: 156160333: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.364: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.366: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.366: 156162025: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.366: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.367: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.368: 156163796: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.368: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.369: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.369: 156165471: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.369: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.371: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.371: 156167206: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.371: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.372: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.373: 156168885: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.373: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.374: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.375: 156170629: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.375: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.376: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.376: 156172361: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.376: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.378: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.379: 156174701: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.379: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.380: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.381: 156176713: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.381: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.382: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.383: 156178682: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.383: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.384: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.384: 156180542: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.384: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.386: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.386: 156182484: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.386: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.388: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.388: 156184281: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.388: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.390: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.390: 156186187: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.390: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.391: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.392: 156188023: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.392: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.393: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.394: 156189883: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.394: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.395: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.396: 156191781: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.396: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.397: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.397: 156193556: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.397: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.399: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.399: 156195514: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.399: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.401: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.401: 156197337: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.401: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.403: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.403: 156199214: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.403: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.405: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.405: 156201097: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.405: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.406: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.407: 156202959: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.407: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.408: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.409: 156204953: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.409: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.410: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.411: 156206805: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.411: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.412: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.413: 156208676: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.413: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.414: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.414: 156210517: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.414: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.416: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.416: 156212348: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.416: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.418: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.418: 156214208: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.418: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.419: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.420: 156216079: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.420: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.421: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.422: 156217968: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.422: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.423: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.424: 156219781: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.424: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.425: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.426: 156221629: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.426: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.427: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.427: 156223450: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.427: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.429: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.429: 156225295: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.429: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.431: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.431: 156227190: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.431: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.432: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.433: 156228972: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.433: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.434: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.435: 156230790: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.435: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.436: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.436: 156232603: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.437: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.438: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.438: 156234429: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.438: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.440: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.440: 156236273: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.440: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.442: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.442: 156238316: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.442: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.444: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.445: 156240829: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.445: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.446: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.446: 156242476: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.446: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.447: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.448: 156244022: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.448: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.449: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.449: 156245580: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.449: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.451: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.451: 156247158: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.451: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.452: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.453: 156248670: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.453: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.454: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.454: 156250297: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.454: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.455: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.456: 156251883: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.456: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.457: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.457: 156253394: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.457: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.458: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.459: 156254930: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.459: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.460: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.460: 156256545: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.460: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.462: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.462: 156258194: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.462: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.463: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.464: 156259894: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.464: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.465: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.465: 156261469: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.465: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.467: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.467: 156263091: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.467: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.468: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.469: 156264727: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.469: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.470: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.470: 156266343: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.470: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.471: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.472: 156267901: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.472: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.473: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.473: 156269397: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.473: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.475: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.475: 156271304: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.475: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.477: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.477: 156273305: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.477: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.478: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.479: 156274866: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.479: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.480: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.480: 156276392: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.480: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.481: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.482: 156277982: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.482: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.483: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.484: 156279629: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.484: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.485: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.485: 156281183: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.485: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.486: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.487: 156282711: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.487: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.488: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.488: 156284277: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.488: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.489: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.490: 156285810: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.490: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.491: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.491: 156287478: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.491: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.493: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.493: 156288991: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.493: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.494: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.494: 156290520: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.494: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.495: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.496: 156292010: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.496: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.497: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.497: 156293576: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.497: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.499: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.499: 156295241: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.499: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.500: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.501: 156296816: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.501: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.502: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.502: 156298395: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.502: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.503: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.504: 156299983: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.504: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.505: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.506: 156302034: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.506: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.507: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.508: 156303962: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.508: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.509: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.509: 156305521: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.509: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.510: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.511: 156307033: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.511: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.512: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.513: 156308620: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.513: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.514: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.514: 156310255: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.514: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.515: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.516: 156311856: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.516: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.517: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.517: 156313371: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.517: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.518: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.519: 156314915: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.519: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.520: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.520: 156316497: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.520: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.522: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.522: 156318056: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.522: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.523: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.524: 156319661: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.524: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.525: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.525: 156321128: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.525: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.526: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.527: 156322631: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.527: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.528: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.528: 156324317: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.528: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.529: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.530: 156325850: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.530: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.531: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.531: 156327510: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.531: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.533: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.533: 156329040: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.533: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.534: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.534: 156330579: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.534: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.536: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.536: 156332174: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.536: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.537: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.538: 156333780: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.538: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.539: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.540: 156335718: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.540: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.541: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.541: 156337269: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.541: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.542: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.543: 156338789: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.543: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.544: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.544: 156340416: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.544: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.545: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.546: 156341902: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.546: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.547: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.547: 156343440: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.547: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.548: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.549: 156345017: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.549: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.550: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.551: 156346612: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.551: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.552: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.552: 156348201: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.552: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.553: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.554: 156349744: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.554: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.555: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.555: 156351299: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.555: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.556: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.557: 156352802: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.557: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.558: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.558: 156354329: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.558: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.559: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.560: 156355936: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.560: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.561: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.561: 156357560: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.561: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.563: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.563: 156359196: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.563: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.564: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.565: 156360776: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.565: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.566: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.566: 156362428: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.566: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.567: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.568: 156363977: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.568: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.569: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.569: 156365557: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.569: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.571: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.571: 156367249: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.571: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.573: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.573: 156369123: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.573: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.574: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.575: 156370640: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.575: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.576: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.576: 156372185: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.576: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.577: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.578: 156373767: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.578: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.579: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.579: 156375388: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.579: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.581: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.581: 156377048: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.581: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.582: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.582: 156378590: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.582: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.584: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.584: 156380236: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.584: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.585: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.586: 156382041: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.586: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.587: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.588: 156383682: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.588: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.589: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.589: 156385246: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.589: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.590: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.591: 156386752: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.591: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.592: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.592: 156388327: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.592: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.593: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.594: 156389793: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.594: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.595: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.595: 156391325: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.595: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.597: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.597: 156393042: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.597: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.598: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.599: 156394633: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.599: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.600: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.600: 156396269: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.600: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.601: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.602: 156397798: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.602: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.603: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.603: 156399502: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.603: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.605: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.605: 156401048: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.605: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.606: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.607: 156402663: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.607: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.608: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.608: 156404239: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.608: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.609: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.610: 156405749: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.610: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.611: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.611: 156407293: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.611: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.612: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.613: 156408836: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.613: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.614: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.614: 156410430: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.614: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.616: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.616: 156412010: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.616: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.617: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.617: 156413577: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.617: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.619: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.619: 156415120: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.619: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.620: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.621: 156416730: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.621: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.622: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.622: 156418463: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.622: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.624: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.624: 156420260: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.624: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.625: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.626: 156421948: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.626: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.627: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.628: 156423744: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.628: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.629: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.629: 156425536: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.629: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.631: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.631: 156427284: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.631: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.632: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.633: 156428929: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.633: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.634: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.635: 156430630: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.635: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.636: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.636: 156432317: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.636: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.637: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.638: 156433847: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.638: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.639: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.639: 156435492: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.639: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.641: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.641: 156437247: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.641: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.642: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.643: 156439073: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.643: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.644: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.645: 156440911: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.645: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.646: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.647: 156442720: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.647: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.648: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.648: 156444457: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.648: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.650: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.650: 156446173: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.650: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.651: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.652: 156447810: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.652: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.653: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.653: 156449417: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.653: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.654: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.655: 156451010: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.655: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.656: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.657: 156452627: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.657: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.658: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.658: 156454271: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.658: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.659: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.660: 156455802: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.660: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.661: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.661: 156457432: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.661: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.662: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.663: 156459030: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.663: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.664: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.665: 156460680: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.665: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.666: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.666: 156462201: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.666: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.667: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.668: 156463787: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.668: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.669: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.669: 156465347: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.669: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.670: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.671: 156466906: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.671: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.672: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.672: 156468561: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.672: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.674: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.674: 156470202: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.674: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.675: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.676: 156471742: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.676: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.677: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.677: 156473252: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.677: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.678: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.679: 156474729: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.679: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.680: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.680: 156476248: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.680: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.681: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.682: 156477836: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.682: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.683: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.683: 156479515: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.683: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.685: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.685: 156481075: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.685: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.686: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.687: 156482640: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.687: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.688: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.688: 156484243: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.688: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.689: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.690: 156485767: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.690: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.691: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.691: 156487326: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.691: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.693: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.693: 156489011: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.693: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.694: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.694: 156490538: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.694: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.696: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.696: 156491985: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.696: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.697: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.697: 156493540: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.697: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.699: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.699: 156495083: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.699: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.700: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.701: 156496675: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.701: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.702: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.702: 156498267: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.702: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.703: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.704: 156499838: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.704: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.705: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.705: 156501395: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.705: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.706: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.707: 156502892: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.707: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.708: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.708: 156504431: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.708: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.709: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.710: 156505938: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.710: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.711: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.711: 156507463: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.711: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.713: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.713: 156509362: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.713: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.714: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.715: 156510831: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.715: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.716: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.716: 156512457: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.716: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.717: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.718: 156514048: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.718: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.719: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.720: 156515634: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.720: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.721: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.721: 156517151: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.721: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.722: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.723: 156518675: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.723: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.724: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.724: 156520251: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.724: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.725: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.726: 156521839: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.726: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.727: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.727: 156523428: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.727: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.728: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.729: 156524973: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.729: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.730: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.731: 156526657: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.731: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.732: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.732: 156528240: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.732: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.733: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.734: 156529736: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.734: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.735: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.735: 156531221: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.735: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.736: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.737: 156532858: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.737: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.738: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.738: 156534401: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.738: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.739: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.740: 156535997: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.740: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.741: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.742: 156537629: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.742: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.743: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.743: 156539232: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.743: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.744: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.745: 156540704: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.745: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.746: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.746: 156542245: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.746: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.747: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.748: 156543780: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.748: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.749: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.749: 156545525: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.749: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.751: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.751: 156547127: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.751: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.752: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.753: 156548822: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.753: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.754: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.754: 156550405: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.754: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.756: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.756: 156552047: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.756: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.757: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.758: 156553634: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.758: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.759: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.759: 156555364: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.759: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.761: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.761: 156557040: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.761: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.762: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.762: 156558579: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.762: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.764: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.764: 156560496: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.764: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.766: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.766: 156562284: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.766: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.767: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.768: 156563855: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.768: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.769: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.769: 156565407: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.769: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.770: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.771: 156566961: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.771: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.772: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.772: 156568555: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.772: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.774: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.774: 156570217: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.774: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.775: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.776: 156571738: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.776: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.777: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.777: 156573417: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.777: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.779: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.779: 156575038: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.779: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.780: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.780: 156576601: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.781: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.782: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.782: 156578148: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.782: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.783: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.784: 156579708: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.784: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.785: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.785: 156581169: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.785: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.786: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.787: 156582704: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.787: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.788: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.788: 156584232: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.788: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.789: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.790: 156585771: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.790: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.791: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.791: 156587360: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.791: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.792: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.793: 156588875: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.793: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.794: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.794: 156590383: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.794: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.795: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.796: 156591934: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.796: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.797: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.797: 156593448: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.797: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.798: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.799: 156594933: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.799: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.800: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.800: 156596521: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.800: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.801: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.802: 156598014: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.802: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.803: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.803: 156599583: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.803: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.805: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.805: 156601107: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.805: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.806: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.806: 156602593: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.806: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.808: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.808: 156604170: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.808: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.809: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.810: 156605654: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.810: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.811: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.811: 156607194: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.811: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.812: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.813: 156608708: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.813: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.814: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.814: 156610190: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.814: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.815: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.816: 156611734: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.816: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.817: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.817: 156613338: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.817: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.818: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.819: 156614833: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.819: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.820: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.820: 156616416: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.820: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.821: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.822: 156618035: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.822: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.823: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.824: 156619660: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.824: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.825: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.825: 156621175: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.825: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.826: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.827: 156622660: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.827: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.828: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.828: 156624227: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.828: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.829: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.830: 156625773: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.830: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.831: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.831: 156627333: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.831: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.832: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.833: 156628808: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.833: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.834: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.834: 156630373: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.834: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.835: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.836: 156631879: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.836: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.837: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.837: 156633362: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.837: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.838: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.839: 156634812: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.839: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.840: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.840: 156636366: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.840: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.841: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.842: 156637903: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.842: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.843: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.843: 156639480: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.843: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.845: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.845: 156641000: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.845: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.846: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.846: 156642473: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.846: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.848: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.848: 156644153: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.848: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.849: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.850: 156645733: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.850: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.851: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.851: 156647231: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.851: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.852: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.853: 156648803: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.853: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.854: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.854: 156650398: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.854: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.855: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.856: 156651920: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.856: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.857: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.857: 156653416: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.857: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.858: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.859: 156654947: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.859: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.860: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.861: 156656878: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.861: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.862: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.863: 156658614: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.863: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.864: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.864: 156660262: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.864: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.865: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.866: 156661801: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.866: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.867: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.867: 156663484: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.867: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.869: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.869: 156665011: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.869: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.870: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.871: 156666803: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.871: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.872: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.872: 156668409: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.872: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.873: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.874: 156669977: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.874: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.875: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.875: 156671463: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.875: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.877: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.877: 156673063: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.877: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.878: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.879: 156674638: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.879: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.880: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.880: 156676165: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.880: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.881: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.882: 156677771: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.882: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.883: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.883: 156679362: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.883: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.884: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.885: 156680860: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.885: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.886: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.886: 156682437: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.886: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.888: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.888: 156684058: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.888: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.889: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.890: 156685642: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.890: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.891: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.891: 156687262: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.891: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.892: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.893: 156688734: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.893: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.894: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.894: 156690317: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.894: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.895: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.896: 156691893: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.896: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.897: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.897: 156693365: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.897: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.898: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.899: 156694921: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.899: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.900: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.900: 156696419: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.900: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.901: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.902: 156697955: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.902: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.903: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.903: 156699493: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.903: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.905: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.905: 156701043: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.905: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.906: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.907: 156702630: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.907: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.908: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.908: 156704239: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.908: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.909: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.910: 156705820: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.910: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.911: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.911: 156707355: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.911: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.912: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.913: 156708833: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.913: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.914: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.914: 156710403: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.914: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.915: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.916: 156711992: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.916: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.917: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.917: 156713518: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.917: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.919: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.919: 156715098: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.919: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.920: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.921: 156716991: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.921: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.922: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.922: 156718424: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.922: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.923: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.924: 156719913: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.924: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.925: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.925: 156721439: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.925: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.927: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.927: 156723014: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.927: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.928: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.928: 156724548: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.928: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.930: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.930: 156726058: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.930: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.931: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.932: 156727648: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.932: write 23 regs 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.933: all registers written 188s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.933: 156729173: ../libfprint/drivers/aes2501.c:310 188s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.933: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.934: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.935: 156730659: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.935: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.936: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.936: 156732221: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.936: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.937: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.938: 156733756: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.938: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.939: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.939: 156735321: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.939: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.940: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.941: 156736855: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.941: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.942: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.942: 156738392: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.942: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.943: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.944: 156739933: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.944: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.945: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.945: 156741569: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.945: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.947: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.947: 156743087: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.947: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.948: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.948: 156744585: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.948: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.950: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.950: 156746152: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.950: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.951: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.952: 156747732: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.952: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.953: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.953: 156749310: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.953: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.954: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.955: 156750900: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.955: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.956: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.956: 156752449: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.956: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.957: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.958: 156754064: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.958: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.959: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.960: 156755626: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.960: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.961: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.961: 156757145: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.961: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.962: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.963: 156758663: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.963: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.964: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.964: 156760156: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.964: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.965: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.966: 156761657: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.966: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.967: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.967: 156763181: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.967: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.968: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.969: 156764670: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.969: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.970: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.970: 156766196: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.970: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.971: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.972: 156767928: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.972: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.973: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.974: 156769672: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.974: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.975: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.975: 156771232: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.975: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.976: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.977: 156772777: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.977: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.978: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.978: 156774319: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.978: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.979: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.980: 156775772: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.980: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.981: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.981: 156777271: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.981: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.982: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.983: 156778859: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.983: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.984: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.984: 156780447: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.984: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.985: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.986: 156781923: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.986: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.987: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.987: 156783458: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.987: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.988: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.989: 156784890: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.989: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.990: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.990: 156786435: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.990: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.991: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.992: 156788017: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.992: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.993: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.993: 156789476: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.993: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.995: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.995: 156791039: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.995: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.996: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.996: 156792600: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.997: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.998: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:36.998: 156794138: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.998: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:36.999: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.000: 156795643: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.000: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.001: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.001: 156797169: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.001: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.002: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.003: 156798695: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.003: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.004: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.004: 156800171: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.004: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.005: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.006: 156801737: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.006: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.007: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.007: 156803194: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.007: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.008: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.009: 156804707: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.009: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.010: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.010: 156806298: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.010: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.011: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.012: 156807815: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.012: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.013: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.013: 156809426: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.013: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.014: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.015: 156810993: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.015: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.016: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.017: 156812718: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.017: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.018: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.018: 156814215: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.018: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.019: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.020: 156815725: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.020: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.021: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.021: 156817267: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.021: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.022: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.023: 156818817: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.023: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.024: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.024: 156820419: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.024: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.025: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.026: 156822041: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.026: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.027: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.027: 156823572: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.027: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.029: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.029: 156825036: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.029: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.030: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.030: 156826549: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.030: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.032: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.032: 156828175: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.032: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.033: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.034: 156829788: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.034: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.035: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.035: 156831444: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.035: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.037: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.037: 156833149: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.037: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.038: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.039: 156834694: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.039: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.040: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.040: 156836384: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.040: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.041: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.042: 156837922: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.042: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.043: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.043: 156839395: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.043: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.044: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.045: 156840925: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.045: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.046: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.046: 156842431: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.046: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.047: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.048: 156843939: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.048: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.049: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.049: 156845546: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.049: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.051: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.051: 156847142: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.051: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.052: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.053: 156848745: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.053: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.054: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.054: 156850237: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.054: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.055: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.056: 156851774: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.056: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.057: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.057: 156853308: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.057: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.058: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.059: 156854885: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.059: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.060: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.060: 156856417: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.060: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.061: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.062: 156857948: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.062: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.063: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.064: 156859697: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.064: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.065: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.065: 156861177: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.065: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.066: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.067: 156862711: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.067: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.068: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.068: 156864405: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.068: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.069: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.070: 156865897: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.070: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.071: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.071: 156867463: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.071: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.073: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.073: 156869258: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.073: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.074: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.075: 156870851: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.075: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.076: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.076: 156872426: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.076: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.078: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.078: 156874147: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.078: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.079: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.080: 156875766: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.080: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.081: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.081: 156877417: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.081: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.082: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.083: 156878853: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.083: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.084: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.084: 156880426: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.084: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.085: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.086: 156881844: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.086: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.087: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.087: 156883396: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.087: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.088: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.089: 156885015: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.089: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.090: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.090: 156886423: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.090: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.091: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.092: 156887952: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.092: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.093: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.093: 156889601: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.094: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.095: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.095: 156891145: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.095: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.096: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.097: 156892621: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.097: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.098: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.098: 156894438: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.098: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.100: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.100: 156896208: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.100: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.101: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.102: 156897704: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.102: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.103: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.103: 156899226: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.103: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.104: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.105: 156900794: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.105: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.106: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.106: 156902382: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.106: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.107: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.108: 156903903: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.108: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.109: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.109: 156905475: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.109: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.110: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.111: 156906916: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.111: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.112: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.112: 156908418: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.112: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.113: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.114: 156909954: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.114: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.115: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.115: 156911575: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.115: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.117: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.117: 156913145: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.117: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.118: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.119: 156914667: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.119: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.120: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.120: 156916184: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.120: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.121: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.122: 156917662: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.122: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.123: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.123: 156919202: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.123: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.124: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.125: 156920840: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.125: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.126: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.126: 156922502: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.126: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.128: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.128: 156924320: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.128: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.129: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.130: 156925889: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.130: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.131: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.131: 156927455: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.131: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.133: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.133: 156929052: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.133: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.134: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.135: 156930616: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.135: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.136: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.136: 156932198: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.136: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.137: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.138: 156933756: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.138: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.139: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.139: 156935368: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.139: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.140: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.141: 156936898: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.141: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.142: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.142: 156938474: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.142: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.144: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.144: 156940046: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.144: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.145: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.146: 156941678: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.146: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.147: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.147: 156943097: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.147: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.148: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.149: 156944632: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.149: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.150: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.150: 156946214: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.150: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.151: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.152: 156947744: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.152: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.153: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.153: 156949317: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.153: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.154: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.155: 156950830: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.155: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.156: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.156: 156952356: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.156: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.157: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.158: 156953960: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.158: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.159: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.159: 156955579: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.159: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.161: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.161: 156957056: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.161: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.162: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.162: 156958602: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.163: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.164: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.164: 156960113: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.164: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.165: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.166: 156961672: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.166: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.167: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.167: 156963256: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.167: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.168: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.169: 156964770: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.169: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.170: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.170: 156966382: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.170: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.171: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.172: 156967910: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.172: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.173: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.173: 156969447: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.173: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.174: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.175: 156970926: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.175: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.176: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.176: 156972427: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.176: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.178: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.178: 156974161: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.178: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.179: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.180: 156975861: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.180: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.181: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.181: 156977436: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.181: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.182: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.183: 156978994: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.183: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.184: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.184: 156980599: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.185: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.186: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.186: 156982157: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.186: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.187: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.188: 156983794: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.188: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.189: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.189: 156985381: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.189: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.190: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.191: 156986928: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.191: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.192: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.192: 156988430: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.192: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.193: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.194: 156990013: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.194: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.195: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.195: 156991428: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.195: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.196: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.197: 156992969: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.197: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.198: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.199: 156994654: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.199: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.200: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.200: 156996255: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.200: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.201: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.202: 156997927: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.202: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.203: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.203: 156999501: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.203: write 23 regs 189s Executing: libfprint-2/driver-aes2501.test 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.205: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.205: 157001469: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.205: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.207: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.207: 157003038: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.207: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.208: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.209: 157004773: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.209: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.210: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.210: 157006389: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.210: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.212: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.212: 157007968: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.212: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.213: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.213: 157009532: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.213: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.215: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.215: 157011208: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.215: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.216: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.217: 157012774: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.217: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.218: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.218: 157014341: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.218: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.219: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.220: 157015807: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.220: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.221: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.221: 157017410: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.221: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.222: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.223: 157018980: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.223: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.224: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.224: 157020584: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.224: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.226: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.226: 157022209: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.226: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.227: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.228: 157023878: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.228: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.229: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.229: 157025465: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.229: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.230: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.231: 157026973: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.231: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.232: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.233: 157028724: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.233: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.234: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.234: 157030317: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.234: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.236: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.236: 157032067: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.236: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.237: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.237: 157033590: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.237: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.239: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.239: 157035180: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.239: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.240: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.241: 157036699: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.241: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.242: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.242: 157038278: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.242: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.243: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.244: 157039833: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.244: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.245: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.245: 157041399: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.245: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.247: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.247: 157043061: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.247: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.248: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.249: 157044678: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.249: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.250: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.250: 157046147: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.250: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.251: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.251: 157047599: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.252: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.253: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.253: 157049221: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.253: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.254: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.255: 157050783: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.255: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.256: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.256: 157052403: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.256: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.257: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.258: 157053980: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.258: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.259: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.259: 157055587: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.259: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.261: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.261: 157057167: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.261: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.262: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.263: 157058660: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.263: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.264: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.264: 157060310: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.264: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.265: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.266: 157061736: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.266: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.267: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.267: 157063306: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.267: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.268: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.269: 157064856: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.269: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.270: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.270: 157066404: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.270: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.272: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.272: 157067990: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.272: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.273: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.274: 157069611: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.274: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.275: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.275: 157071202: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.275: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.276: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.277: 157072735: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.277: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.278: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.278: 157074255: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.278: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.279: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.280: 157075819: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.280: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.281: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.281: 157077368: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.281: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.282: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.283: 157078905: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.283: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.284: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.284: 157080486: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.284: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.285: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.286: 157081998: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.286: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.287: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.287: 157083581: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.287: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.289: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.289: 157085114: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.289: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.290: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.291: 157086627: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.291: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.292: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.292: 157088156: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.292: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.293: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.294: 157089645: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.294: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.295: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.295: 157091150: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.295: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.296: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.297: 157092711: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.297: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.298: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.298: 157094182: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.298: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.299: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.300: 157095803: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.300: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.301: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.301: 157097429: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.301: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.302: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.303: 157098906: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.303: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.304: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.304: 157100413: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.304: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.306: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.306: 157102062: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.306: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.307: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.308: 157103653: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.308: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.309: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.309: 157105221: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.309: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.310: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.311: 157106846: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.311: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.312: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.312: 157108408: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.312: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.313: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.314: 157109975: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.314: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.315: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.315: 157111487: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.315: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.316: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.317: 157113021: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.317: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.318: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.318: 157114461: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.318: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.319: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.320: 157115987: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.320: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.321: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.321: 157117436: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.321: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.322: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.323: 157118941: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.323: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.324: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.324: 157120430: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.324: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.325: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.326: 157121907: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.326: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.327: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.327: 157123453: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.327: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.328: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.329: 157124941: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.329: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.330: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.330: 157126562: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.331: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.332: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.332: 157128203: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.332: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.333: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.334: 157129950: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.334: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.335: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.336: 157131791: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.336: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.337: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.338: 157133787: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.338: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.339: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.339: 157135560: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.339: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.341: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.341: 157137179: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.341: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.342: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.343: 157138867: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.343: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.344: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.344: 157140470: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.344: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.345: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.346: 157141976: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.346: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.347: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.347: 157143479: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.347: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.349: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.349: 157145050: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.349: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.350: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.350: 157146560: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.350: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.352: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.352: 157148113: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.352: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.353: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.354: 157149793: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.354: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.355: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.356: 157151689: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.356: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.357: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.357: 157153297: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.357: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.358: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.359: 157154815: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.359: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.360: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.360: 157156420: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.360: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.361: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.362: 157157923: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.362: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.363: all registers written 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.363: 157159434: ../libfprint/drivers/aes2501.c:310 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.363: write 23 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.364: all registers written 189s (process:4220): libfprint-device-DEBUG: 20:26:37.365: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.365: Image device reported finger status: on 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.365: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.365: 157161038: ../libfprint/drivers/aes2501.c:581 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.365: [aes2501] CAPTURE_NUM_STATES entering state 0 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.365: write 26 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.366: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.366: [aes2501] CAPTURE_NUM_STATES entering state 1 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.366: [aes2501] CAPTURE_NUM_STATES entering state 2 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.366: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.367: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.367: [aes2501] CAPTURE_NUM_STATES entering state 3 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.367: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.367: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.368: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.368: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.368: sum=5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.368: ADREFHI is 50 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.368: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.368: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.368: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.368: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.369: sum=8 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.369: ADREFHI is 48 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.369: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.369: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.369: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.369: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.370: sum=19 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.370: ADREFHI is 40 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.370: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.370: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.370: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.370: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.371: sum=60 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.371: ADREFHI is 38 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.371: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.371: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.371: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.371: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.371: sum=123 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.372: ADREFHI is 30 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.372: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.372: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.372: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.372: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.372: sum=226 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.372: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.372: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.372: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.373: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.373: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.373: sum=461 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.373: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.373: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.373: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.374: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.374: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.374: sum=466 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.374: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.374: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.374: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.374: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.374: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.375: sum=465 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.375: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.375: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.375: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.375: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.375: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.376: sum=620 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.376: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.376: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.376: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.376: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.376: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.377: sum=629 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.377: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.377: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.377: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.377: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.377: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.377: sum=615 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.377: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.377: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.377: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.378: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.378: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.378: sum=585 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.378: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.378: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.378: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.379: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.379: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.379: sum=581 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.379: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.379: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.379: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.380: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.380: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.380: sum=418 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.380: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.380: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.380: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.380: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.380: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.381: sum=406 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.381: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.381: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.381: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.381: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.381: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.382: sum=389 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.382: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.382: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.382: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.382: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.382: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.383: sum=388 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.383: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.383: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.383: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.383: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.383: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.384: sum=393 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.384: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.384: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.384: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.384: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.384: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.385: sum=389 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.385: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.385: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.385: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.385: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.385: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.385: sum=379 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.385: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.385: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.385: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.386: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.386: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.386: sum=361 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.386: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.386: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.386: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.387: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.387: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.387: sum=356 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.387: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.387: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.387: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.388: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.388: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.388: sum=193 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.388: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.388: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.388: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.388: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.388: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.389: sum=178 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.389: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.389: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.389: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.389: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.389: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.390: sum=164 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.390: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.390: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.390: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.390: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.390: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.391: sum=157 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.391: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.391: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.391: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.391: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.391: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.392: sum=152 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.392: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.392: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.392: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.392: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.392: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.392: sum=154 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.392: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.393: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.393: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.393: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.393: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.393: sum=157 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.393: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.393: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.393: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.394: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.394: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.394: sum=161 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.394: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.394: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.394: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.395: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.395: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.395: sum=161 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.395: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.395: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.395: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.395: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.395: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.396: sum=161 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.396: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.396: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.396: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.396: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.396: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.397: sum=162 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.397: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.397: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.397: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.397: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.397: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.398: sum=166 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.398: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.398: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.398: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.398: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.398: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.398: sum=143 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.398: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.398: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.398: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.399: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.399: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.399: sum=106 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.399: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.399: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.399: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.400: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.400: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.400: sum=74 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.400: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.400: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.400: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.400: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.400: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.401: sum=51 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.401: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.401: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.401: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.401: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.401: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.402: sum=40 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.402: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.402: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.402: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.402: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.402: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.402: sum=39 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.402: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.402: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.402: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.403: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.403: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.403: sum=19 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.403: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.403: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.403: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.404: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.404: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.404: sum=13 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.404: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.404: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.404: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.404: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.404: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.405: sum=5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.405: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.405: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.405: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.405: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.405: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.406: sum=2 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.406: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.406: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.406: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.406: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.406: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.407: sum=0 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.407: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.407: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.407: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.407: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.407: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.407: sum=0 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.407: ADREFHI is 28 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.407: [aes2501] CAPTURE_NUM_STATES entering state 4 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.407: write 7 regs 189s (process:4220): libfprint-aeslib-DEBUG: 20:26:37.408: all registers written 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.408: [aes2501] CAPTURE_NUM_STATES entering state 5 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.408: sum=0 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.408: ADREFHI is 28 189s (process:4220): libfprint-assembling-DEBUG: 20:26:37.466: calc delta completed in 0.058155 secs 189s (process:4220): libfprint-assembling-DEBUG: 20:26:37.525: calc delta completed in 0.058076 secs 189s (process:4220): libfprint-assembling-DEBUG: 20:26:37.525: errors: 53228 rev: 72653 189s (process:4220): libfprint-assembling-DEBUG: 20:26:37.583: calc delta completed in 0.058114 secs 189s (process:4220): libfprint-assembling-DEBUG: 20:26:37.583: height is 102 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.583: Image device captured an image 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.584: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 189s (process:4220): libfprint-device-DEBUG: 20:26:37.584: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:4220): libfprint-device-DEBUG: 20:26:37.584: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.584: Image device reported finger status: off 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.584: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.584: Deactivating image device 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.584: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 189s (process:4220): libfprint-SSM-DEBUG: 20:26:37.584: [aes2501] CAPTURE_NUM_STATES completed successfully 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.584: 157379922: ../libfprint/drivers/aes2501.c:547 189s (process:4220): libfprint-aes2501-DEBUG: 20:26:37.584: 157379926: ../libfprint/drivers/aes2501.c:820 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.584: Image device deactivation completed 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.584: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 189s (process:4220): libfprint-image-DEBUG: 20:26:37.589: Minutiae scan completed in 0.005512 secs 189s (process:4220): libfprint-device-DEBUG: 20:26:37.589: Device reported capture completion 189s (process:4220): libfprint-device-DEBUG: 20:26:37.589: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 189s (process:4220): libfprint-device-DEBUG: 20:26:37.589: Updated temperature model after 1.27 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s (process:4220): libfprint-image_device-DEBUG: 20:26:37.590: Image device close completed 189s (process:4220): libfprint-device-DEBUG: 20:26:37.590: Device reported close completion 189s (process:4220): libfprint-device-DEBUG: 20:26:37.590: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:4220): libfprint-device-DEBUG: 20:26:37.590: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s ** (umockdev-run:4216): DEBUG: 20:26:37.633: umockdev.vala:154: Removing test bed /tmp/umockdev.7RU312 189s (umockdev-run:4216): GLib-DEBUG: 20:26:37.638: unsetenv() is not thread-safe and should not be used after threads are created 189s Comparing PNGs /tmp/libfprint-umockdev-test-_aa_kc6e/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 189s PASS: libfprint-2/driver-aes2501.test 189s Running test: libfprint-2/driver-aes3500.test 189s ** (umockdev-run:4229): DEBUG: 20:26:37.686: umockdev.vala:127: Created udev test bed /tmp/umockdev.TXFE22 189s ** (umockdev-run:4229): DEBUG: 20:26:37.687: umockdev.vala:1414: 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 189s ** (umockdev-run:4229): DEBUG: 20:26:37.688: umockdev.vala:1492: 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) 189s ** (umockdev-run:4229): DEBUG: 20:26:37.692: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXFE22/dev/bus/usb/003/004 189s ** (umockdev-run:4229): DEBUG: 20:26:37.692: umockdev.vala:1414: 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 189s ** (umockdev-run:4229): DEBUG: 20:26:37.694: umockdev.vala:1492: 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) 189s ** (umockdev-run:4229): DEBUG: 20:26:37.696: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXFE22/dev/bus/usb/003/003 189s ** (umockdev-run:4229): DEBUG: 20:26:37.697: umockdev.vala:1414: 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 189s ** (umockdev-run:4229): DEBUG: 20:26:37.698: umockdev.vala:1492: 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) 189s ** (umockdev-run:4229): DEBUG: 20:26:37.701: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXFE22/dev/bus/usb/003/002 189s ** (umockdev-run:4229): DEBUG: 20:26:37.701: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 189s ** (umockdev-run:4229): DEBUG: 20:26:37.702: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0/usb3 (subsystem usb) 189s ** (umockdev-run:4229): DEBUG: 20:26:37.705: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.TXFE22/dev/bus/usb/003/001 189s ** (umockdev-run:4229): DEBUG: 20:26:37.706: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 189s ** (umockdev-run:4229): DEBUG: 20:26:37.706: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0/0000:39:00.0 (subsystem pci) 189s ** (umockdev-run:4229): DEBUG: 20:26:37.709: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 189s ** (umockdev-run:4229): DEBUG: 20:26:37.710: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 189s ** (umockdev-run:4229): DEBUG: 20:26:37.712: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 189s ** (umockdev-run:4229): DEBUG: 20:26:37.713: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 189s ** (umockdev-run:4229): DEBUG: 20:26:37.715: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0 189s ** (umockdev-run:4229): DEBUG: 20:26:37.716: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 189s (umockdev-run:4229): GLib-GIO-DEBUG: 20:26:37.718: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 189s (process:4233): libfprint-context-DEBUG: 20:26:37.793: Initializing FpContext (libfprint version 1.94.8+tod1) 189s (process:4233): libfprint-tod-DEBUG: 20:26:37.793: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 189s (process:4233): libfprint-context-DEBUG: 20:26:37.797: No driver found for USB device 2230:0006 189s (process:4233): libfprint-context-DEBUG: 20:26:37.797: No driver found for USB device 2230:0006 189s (process:4233): libfprint-context-DEBUG: 20:26:37.797: No driver found for USB device 1D6B:0002 189s (process:4233): libfprint-device-DEBUG: 20:26:37.797: Device reported probe completion 189s (process:4233): libfprint-device-DEBUG: 20:26:37.797: Completing action FPI_DEVICE_ACTION_PROBE in idle! 189s (process:4233): libfprint-device-DEBUG: 20:26:37.797: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.798: Image device open completed 189s (process:4233): libfprint-device-DEBUG: 20:26:37.798: Device reported open completion 189s (process:4233): libfprint-device-DEBUG: 20:26:37.798: Completing action FPI_DEVICE_ACTION_OPEN in idle! 189s (process:4233): libfprint-device-DEBUG: 20:26:37.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:4233): libfprint-device-DEBUG: 20:26:37.799: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.799: Activating image device 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.799: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 189s (process:4233): libfprint-aeslib-DEBUG: 20:26:37.799: write 50 regs 189s (process:4233): libfprint-aeslib-DEBUG: 20:26:37.802: all registers written 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.802: Image device activation completed 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.802: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 189s (process:4233): libfprint-aeslib-DEBUG: 20:26:37.802: write 6 regs 189s (process:4233): libfprint-device-DEBUG: 20:26:37.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED 189s (process:4233): libfprint-aeslib-DEBUG: 20:26:37.804: all registers written 189s (process:4233): libfprint-device-DEBUG: 20:26:37.804: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.804: Image device reported finger status: on 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.804: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e0 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e1 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e2 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e3 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e4 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e5 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e6 189s (process:4233): libfprint-aes3k-DEBUG: 20:26:37.804: frame header byte e7 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Image device captured an image 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 189s (process:4233): libfprint-device-DEBUG: 20:26:37.805: Device reported finger status change: FP_FINGER_STATUS_PRESENT 189s (process:4233): libfprint-device-DEBUG: 20:26:37.805: Device reported finger status change: FP_FINGER_STATUS_NONE 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Image device reported finger status: off 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Deactivating image device 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Image device deactivation completed 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.805: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 189s (process:4233): libfprint-image-DEBUG: 20:26:37.827: Minutiae scan completed in 0.021532 secs 189s (process:4233): libfprint-device-DEBUG: 20:26:37.827: Device reported capture completion 189s (process:4233): libfprint-device-DEBUG: 20:26:37.827: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 189s (process:4233): libfprint-device-DEBUG: 20:26:37.827: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 189s (process:4233): libfprint-image_device-DEBUG: 20:26:37.827: Image device close completed 189s (process:4233): libfprint-device-DEBUG: 20:26:37.827: Device reported close completion 189s (process:4233): libfprint-device-DEBUG: 20:26:37.827: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 189s (process:4233): libfprint-device-DEBUG: 20:26:37.827: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 189s ** (umockdev-run:4229): DEBUG: 20:26:37.907: umockdev.vala:154: Removing test bed /tmp/umockdev.TXFE22 189s (umockdev-run:4229): GLib-DEBUG: 20:26:37.919: unsetenv() is not thread-safe and should not be used after threads are created 189s Comparing PNGs /tmp/libfprint-umockdev-test-20fhurrm/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 190s PASS: libfprint-2/driver-aes3500.test 190s Running test: libfprint-2/driver-vfs7552.test 190s ** (umockdev-run:4242): DEBUG: 20:26:37.977: umockdev.vala:127: Created udev test bed /tmp/umockdev.U6FJ22 190s ** (umockdev-run:4242): DEBUG: 20:26:37.978: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 190s ** (umockdev-run:4242): DEBUG: 20:26:37.978: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 190s ** (umockdev-run:4242): DEBUG: 20:26:37.982: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.U6FJ22/dev/bus/usb/001/003 190s ** (umockdev-run:4242): DEBUG: 20:26:37.982: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 190s ** (umockdev-run:4242): DEBUG: 20:26:37.983: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 190s ** (umockdev-run:4242): DEBUG: 20:26:37.986: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.U6FJ22/dev/bus/usb/001/001 190s ** (umockdev-run:4242): DEBUG: 20:26:37.986: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 190s ** (umockdev-run:4242): DEBUG: 20:26:37.986: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 190s (umockdev-run:4242): GLib-GIO-DEBUG: 20:26:37.989: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 190s (process:4246): libfprint-context-DEBUG: 20:26:38.073: Initializing FpContext (libfprint version 1.94.8+tod1) 190s (process:4246): libfprint-tod-DEBUG: 20:26:38.074: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 190s (process:4246): libfprint-context-DEBUG: 20:26:38.075: No driver found for USB device 1D6B:0002 190s (process:4246): libfprint-device-DEBUG: 20:26:38.076: Device reported probe completion 190s (process:4246): libfprint-device-DEBUG: 20:26:38.076: Completing action FPI_DEVICE_ACTION_PROBE in idle! 190s (process:4246): libfprint-device-DEBUG: 20:26:38.076: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.077: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.077: [vfs7552] DEVICE OPEN entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.077: Sending vfs7552_cmd_01 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.078: [vfs7552] DEVICE OPEN entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.078: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.078: Got 38 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.078: [vfs7552] DEVICE OPEN entering state 2 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.078: Sending vfs7552_cmd_19 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.079: [vfs7552] DEVICE OPEN entering state 3 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.079: Receiving 128 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.079: Got 68 bytes out of 128 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.080: [vfs7552] DEVICE OPEN entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.080: Sending vfs7552_init_00 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.080: [vfs7552] DEVICE OPEN entering state 5 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.080: Receiving 64 bytes 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.081: [vfs7552] DEVICE OPEN entering state 6 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.081: Sending vfs7552_init_01 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.081: [vfs7552] DEVICE OPEN entering state 7 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.081: Receiving 64 bytes 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.082: [vfs7552] DEVICE OPEN entering state 8 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.082: Sending vfs7552_init_02 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.082: [vfs7552] DEVICE OPEN entering state 9 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.083: Receiving 64 bytes 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.083: [vfs7552] DEVICE OPEN entering state 10 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.083: Sending vfs7552_init_03 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.084: [vfs7552] DEVICE OPEN entering state 11 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.084: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.084: Got 10 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.084: [vfs7552] DEVICE OPEN entering state 12 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.084: Sending vfs7552_init_04 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.085: [vfs7552] DEVICE OPEN entering state 13 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.085: Receiving 64 bytes 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.085: [vfs7552] DEVICE OPEN completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.085: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 190s (process:4246): libfprint-image_device-DEBUG: 20:26:38.085: Image device open completed 190s (process:4246): libfprint-device-DEBUG: 20:26:38.085: Device reported open completion 190s (process:4246): libfprint-device-DEBUG: 20:26:38.086: Completing action FPI_DEVICE_ACTION_OPEN in idle! 190s (process:4246): libfprint-device-DEBUG: 20:26:38.086: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:4246): libfprint-device-DEBUG: 20:26:38.086: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 190s (process:4246): libfprint-image_device-DEBUG: 20:26:38.086: Activating image device 190s (process:4246): libfprint-image_device-DEBUG: 20:26:38.086: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 190s (process:4246): libfprint-image_device-DEBUG: 20:26:38.086: Image device activation completed 190s (process:4246): libfprint-image_device-DEBUG: 20:26:38.086: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 190s (process:4246): libfprint-image_device-DEBUG: 20:26:38.086: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 190s (process:4246): libfprint-device-DEBUG: 20:26:38.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.136: changing to 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.136: [vfs7552] ACTIVATE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.136: [vfs7552] ACTIVATE INIT entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.136: Sending vfs7552_image_start 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.136: [vfs7552] ACTIVATE INIT entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.136: Receiving 2048 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.137: Got 1962 bytes out of 2048 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.137: [vfs7552] ACTIVATE INIT completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.137: [vfs7552] ACTIVATE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.137: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.137: Receiving 8 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.137: Got 5 bytes out of 8 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.137: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.137: [vfs7552] ACTIVATE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.137: [vfs7552] ACTIVATE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.137: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.137: Receiving 8 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.138: Got 5 bytes out of 8 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.138: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.138: [vfs7552] ACTIVATE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.138: [vfs7552] ACTIVATE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.138: [vfs7552] ACTIVATE_NUM_STATES completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.138: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.138: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.138: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.139: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.139: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.139: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.139: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.139: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.140: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.140: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.140: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.140: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.140: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.140: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.141: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.141: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.141: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.141: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.141: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.141: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.142: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.142: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.142: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.142: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.143: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.143: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.143: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.143: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.143: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.144: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.144: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.144: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.144: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.144: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.144: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.145: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.145: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.145: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.146: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.146: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.146: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.146: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.146: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.147: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.147: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.147: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.147: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.147: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.147: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.148: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.148: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.148: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.148: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.148: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.148: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.149: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.149: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.149: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.149: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.149: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.149: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.150: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.150: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.150: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.150: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.150: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.150: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.151: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.151: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.151: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.151: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.151: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.151: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.152: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.152: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.152: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.152: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.152: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.153: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.153: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.153: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.153: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.153: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.154: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.154: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.154: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.154: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.154: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.154: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.155: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.155: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.155: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.155: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.155: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.155: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.156: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.156: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.156: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.156: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.156: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.156: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.157: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.157: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.157: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.157: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.158: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.158: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.158: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.158: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.158: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.158: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.159: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.159: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.159: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.159: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.160: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.160: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.160: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.160: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.160: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.160: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.161: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.161: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.161: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.161: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.161: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.161: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.162: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.162: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.162: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.162: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.162: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.162: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.163: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.163: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.163: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.163: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.163: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.163: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.164: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.164: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.164: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.164: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.164: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.165: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.165: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.165: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.165: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.165: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.166: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.166: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.166: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.166: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.166: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.166: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.167: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.167: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.167: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.167: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.167: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.167: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.168: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.168: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.169: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.169: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.169: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.169: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.169: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.169: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.170: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.170: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.170: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.170: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.170: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.170: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.171: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.171: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.171: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.171: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.171: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.171: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.172: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.172: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.172: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.172: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.172: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.172: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.173: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.173: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.173: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.173: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.173: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.173: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.174: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.174: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.174: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.174: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.174: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.174: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.175: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.175: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.175: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.175: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.175: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.175: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.175: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.175: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.176: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.176: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.176: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.176: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.176: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.176: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.177: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.177: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.177: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.177: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.177: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.177: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.178: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.178: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.178: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.178: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.178: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.178: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.179: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.179: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.179: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.179: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.179: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.179: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.179: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.180: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.180: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.180: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.180: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.180: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.181: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.181: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.181: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.181: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.181: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.181: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.182: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.182: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.182: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.182: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.182: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.182: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.183: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.183: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.183: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.183: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.183: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.183: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.184: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.184: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.184: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.184: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.184: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.184: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.185: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.185: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.185: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.185: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.185: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.185: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.185: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.186: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.186: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.186: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.186: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.186: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.186: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.186: Receiving 64 bytes 190s (process:4246): libfprint-device-DEBUG: 20:26:38.187: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.187: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.187: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.187: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.187: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.187: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.187: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.188: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.188: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.188: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.188: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.188: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.188: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.189: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.189: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.189: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.189: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.189: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.189: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.190: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.190: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.190: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.190: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.190: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.190: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.191: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.191: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.191: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.191: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.191: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.191: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.192: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.192: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.192: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.192: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.192: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.192: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.193: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.193: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.193: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.193: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.193: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.193: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.194: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.194: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.194: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.194: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.194: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.194: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.195: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.195: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.195: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.195: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.195: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.195: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.196: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.196: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.196: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.196: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.196: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.196: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.197: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.197: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.197: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.197: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.197: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.197: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.198: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.198: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.198: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.198: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.198: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.198: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.199: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.199: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.199: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.199: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.199: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.199: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.200: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.200: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.200: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.200: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.200: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.200: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.201: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.201: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.201: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.201: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.201: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.201: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.202: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.202: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.202: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.202: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.202: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.202: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.203: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.203: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.203: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.203: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.203: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.203: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.204: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.204: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.204: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.204: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.204: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.204: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.205: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.205: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.205: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.205: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.205: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.205: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.206: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.206: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.206: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.206: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.206: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.206: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.207: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.207: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.207: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.207: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.207: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.207: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.208: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.208: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.208: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.208: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.208: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.208: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.209: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.209: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.209: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.209: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.209: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.209: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.210: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.210: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.210: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.210: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.210: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.210: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.211: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.211: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.211: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.211: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.211: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.211: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.212: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.212: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.212: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.212: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.212: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.212: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.213: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.213: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.213: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.213: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.213: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.213: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.214: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.214: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.214: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.214: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.214: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.214: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.215: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.215: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.215: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.215: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.215: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.215: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.216: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.216: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.216: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.216: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.216: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.216: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.217: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.217: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.217: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.217: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.217: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.217: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.218: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.218: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.218: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.218: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.218: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.218: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.219: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.219: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.219: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.219: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.219: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.219: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.220: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.220: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.220: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.220: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.220: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.220: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.221: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.221: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.221: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.221: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.221: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.221: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.222: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.222: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.222: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.222: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.222: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.222: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.223: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.223: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.223: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.223: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.223: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.223: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.224: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.224: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.224: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.224: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.224: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.224: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.225: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.225: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.225: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.225: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.225: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.225: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.226: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.226: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.226: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.226: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.226: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.226: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.227: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.227: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.227: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.227: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.227: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.227: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.228: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.228: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.228: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.228: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.228: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.228: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.229: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.229: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.229: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.229: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.229: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.229: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.229: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.230: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.230: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.230: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.230: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.230: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.231: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.231: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.231: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.231: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.231: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.232: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.232: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.232: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.232: variance_before = 396 190s 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.232: background stored 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.232: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.232: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.233: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.233: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.233: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.233: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.233: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.233: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.234: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.234: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.234: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.234: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.234: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.234: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.235: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.235: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.235: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.235: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.235: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.235: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.236: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.236: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.236: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.236: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.236: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.236: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.237: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.237: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.237: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.237: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.237: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.237: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.238: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.238: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.238: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.238: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.238: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.238: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.239: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.239: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.239: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.239: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.239: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.239: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.240: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.240: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.240: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.240: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.240: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.240: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.241: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.241: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.241: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.241: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.241: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.241: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.241: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.241: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.242: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.242: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.242: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.242: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.242: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.242: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.243: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.243: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.243: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.243: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.243: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.243: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.244: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.244: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.244: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.244: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.244: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.244: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.245: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.245: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.245: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.245: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.245: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.245: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.246: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.246: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.246: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.246: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.246: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.246: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.247: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.247: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.247: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.247: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.247: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.247: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.248: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.248: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.248: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.248: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.248: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.248: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.249: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.249: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.249: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.249: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.249: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.249: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.250: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.250: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.250: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.250: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.250: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.250: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.251: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.251: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.251: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.251: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.251: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.251: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.252: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.252: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.252: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.252: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.252: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.252: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.253: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.253: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.253: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.253: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.253: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.253: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.254: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.254: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.254: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.254: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.254: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.254: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.255: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.255: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.255: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.255: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.255: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.255: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.255: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.256: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.256: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.256: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.256: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.256: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.257: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.257: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.257: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.257: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.257: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.257: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.258: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.258: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.258: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.258: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.258: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.258: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.259: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.259: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.259: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.259: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.259: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.259: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.260: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.260: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.260: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.260: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.260: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.260: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.261: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.261: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.261: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.261: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.261: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.261: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.261: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.261: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.262: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.262: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.262: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.262: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.262: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.262: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.263: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.263: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.263: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.263: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.263: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.263: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.264: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.264: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.264: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.264: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.264: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.264: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.265: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.265: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.265: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.265: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.265: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.265: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.266: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.266: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.266: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.266: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.266: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.266: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.267: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.267: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.267: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.267: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.267: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.267: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.268: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.268: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.268: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.268: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.268: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.268: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.269: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.269: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.269: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.269: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.269: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.269: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.270: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.270: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.270: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.270: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.270: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.270: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.271: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.271: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.271: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.271: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.271: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.271: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.271: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.272: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.272: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.272: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.272: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.272: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.272: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.272: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.273: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.273: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.273: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.273: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.273: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.273: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.274: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.274: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.274: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.274: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.274: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.274: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.275: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.275: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.275: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.275: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.275: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.275: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.276: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.276: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.276: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.276: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.276: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.276: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.277: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.277: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.277: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.277: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.277: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.277: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.278: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.278: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.278: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.278: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.278: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.278: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.279: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.279: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.279: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.279: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.279: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.279: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.280: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.280: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.280: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.280: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.280: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.280: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.281: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.281: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.281: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.281: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.281: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.281: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.282: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.282: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.282: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.283: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.283: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.283: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.283: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.283: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.284: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.284: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.284: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.284: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.284: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.284: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.285: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.285: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.285: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.285: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.285: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.286: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.286: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.286: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.286: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.286: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.287: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.287: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.287: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.287: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.287: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.287: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.288: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.288: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.288: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.288: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.289: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.289: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.289: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.289: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.289: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.290: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.290: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.290: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.290: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.290: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.291: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.291: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.291: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.291: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.291: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.291: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.292: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.292: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.292: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.292: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.292: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.292: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.293: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.293: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.293: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.293: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.293: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.293: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.294: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.294: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.294: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.294: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.294: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.294: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.295: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.295: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.295: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.295: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.295: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.295: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.296: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.296: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.296: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.296: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.296: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.296: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.297: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.297: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.297: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.297: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.298: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.298: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.298: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.298: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.298: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.298: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.299: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.299: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.299: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.299: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.299: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.299: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.300: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.300: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.300: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.300: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.300: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.300: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.301: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.301: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.301: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.301: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.301: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.301: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.302: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.302: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.303: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.303: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.303: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.303: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.303: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.303: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.304: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.304: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.304: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.304: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.304: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.304: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.305: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.305: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.305: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.305: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.305: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.305: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.306: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.306: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.306: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.306: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.307: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.307: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.307: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.307: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.307: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.307: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.308: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.308: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.308: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.309: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.309: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.309: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.309: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.309: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.310: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.310: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.310: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.310: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.310: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.310: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.311: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.311: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.311: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.311: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.311: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.311: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.312: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.312: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.312: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.312: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.312: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.313: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.313: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.313: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.313: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.313: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.314: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.314: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.314: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.314: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.314: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.314: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.315: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.315: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.315: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.315: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.315: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.315: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.316: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.316: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.316: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.316: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.316: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.316: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.317: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.317: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.317: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.317: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.317: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.317: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.318: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.318: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.318: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.319: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.319: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.319: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.319: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.319: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.320: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.320: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.320: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.320: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.320: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.320: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.321: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.321: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.321: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.321: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.321: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.321: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.322: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.322: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.322: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.322: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.322: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.323: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.323: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.323: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.323: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.323: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.324: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.324: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.324: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.324: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.324: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.324: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.325: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.325: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.325: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.325: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.325: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.325: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.326: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.326: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.326: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.326: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.326: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.326: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.327: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.327: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.327: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.327: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.327: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.327: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.328: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.328: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.329: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.329: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.329: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.329: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.329: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.329: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.330: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.330: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.330: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.330: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.330: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.330: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.331: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.331: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.331: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.331: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.331: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.331: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.332: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.332: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.332: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.332: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.332: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.332: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.333: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.333: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.333: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.333: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.333: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.333: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.334: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.334: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.334: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.334: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.334: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.335: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.335: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.335: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.335: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.335: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.335: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.335: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.336: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.336: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.336: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.336: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.337: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.337: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.337: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.337: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.337: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.337: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.338: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.338: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.338: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.338: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.338: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.338: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.339: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.339: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.339: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.340: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.340: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.340: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.340: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.340: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.340: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.341: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.341: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.341: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.341: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.341: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.342: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.342: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.342: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.342: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.342: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.343: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.343: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.343: variance_after = 20 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.343: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.343: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.343: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.343: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.344: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.344: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.344: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.344: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.344: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.344: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.345: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.345: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.345: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.345: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.345: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.346: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.346: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.346: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.346: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.346: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.346: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.347: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.347: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.347: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.347: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.347: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.348: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.348: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.348: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.348: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.348: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.348: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.349: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.349: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.349: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.349: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.349: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.349: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.350: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.350: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.350: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.351: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.351: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.351: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.351: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.351: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.351: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.352: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.352: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.352: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.352: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.352: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.353: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.353: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.353: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.353: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.353: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.353: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.354: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.354: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.354: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.354: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.354: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.354: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.355: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.355: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.355: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.355: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.355: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.355: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.356: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.356: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.356: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.356: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.356: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.356: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.357: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.357: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.357: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.357: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.357: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.357: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.358: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.358: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.358: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.358: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.358: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.358: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.359: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.359: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.359: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.359: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.360: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.360: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.360: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.360: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.360: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.360: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.361: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.361: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.361: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.361: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.361: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.361: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.362: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.362: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.362: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.362: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.362: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.362: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.363: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.363: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.364: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.364: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.364: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.364: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.364: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.364: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.365: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.365: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.365: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.365: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.365: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.365: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.366: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.366: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.366: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.366: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.366: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.366: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.367: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.367: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.367: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.367: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.367: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.367: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.368: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.368: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.368: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.368: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.368: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.368: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.369: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.369: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.369: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.369: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.369: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.369: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.370: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.370: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.370: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.370: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.370: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.370: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.371: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.371: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.371: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.371: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.371: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.371: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.372: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.372: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.372: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.372: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.372: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.372: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.373: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.373: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.373: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.373: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.373: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.373: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.374: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.374: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.374: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.374: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.374: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.374: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.375: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.375: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.375: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.375: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.375: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.375: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.376: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.376: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.376: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.376: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.376: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.376: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.377: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.377: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.378: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.378: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.378: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.378: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.378: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.378: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.379: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.379: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.379: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.379: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.379: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.379: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.380: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.380: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.380: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.380: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.380: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.380: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.381: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.381: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.381: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.381: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.381: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.381: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.382: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.382: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.382: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.382: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.382: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.382: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.383: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.383: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.383: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.383: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.383: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.383: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.384: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.384: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.384: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.384: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.384: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.384: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.385: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.385: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.385: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.385: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.385: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.385: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.386: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.386: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.386: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.386: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.386: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.386: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.387: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.387: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.387: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.387: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.387: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.387: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.388: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.388: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.388: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.388: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.388: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.388: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.389: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.389: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.389: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.389: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.389: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.389: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.390: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.390: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.390: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.390: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.390: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.390: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.391: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.391: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.391: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.391: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.391: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.391: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.391: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.392: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.392: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.392: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.392: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.392: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.393: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.393: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.393: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.393: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.393: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.393: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.394: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.394: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.394: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.394: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.394: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.394: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.395: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.395: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.395: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.395: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.395: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.395: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.396: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.396: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.396: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.396: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.396: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.396: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.397: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.397: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.397: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.397: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.397: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.397: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.398: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.398: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.398: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.398: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.398: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.398: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.399: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.399: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.399: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.399: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.399: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.399: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.400: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.400: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.400: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.400: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.400: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.400: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.401: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.401: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.401: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.401: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.401: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.401: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.402: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.402: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.402: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.402: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.402: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.402: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.402: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.403: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.403: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.403: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.403: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.403: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.403: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.403: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.404: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.404: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.404: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.404: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.404: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.405: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.405: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.405: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.405: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.405: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.405: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.406: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.406: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.406: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.406: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.406: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.406: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.406: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.406: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.407: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.407: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.407: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.407: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.407: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.408: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.408: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.408: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.408: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.408: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.409: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.409: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.409: variance_after = 18 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.409: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.409: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.410: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.410: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.410: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.410: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.410: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.410: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.410: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.410: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.411: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.411: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.411: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.411: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.411: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.411: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.412: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.412: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.412: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.412: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.412: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.412: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.413: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.413: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.413: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.413: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.413: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.413: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.414: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.414: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.414: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.414: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.414: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.414: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.415: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.415: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.415: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.415: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.416: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.416: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.416: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.416: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.416: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.416: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.417: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.417: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.417: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.417: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.417: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.417: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.418: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.418: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.418: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.418: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.418: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.418: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.419: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.419: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.419: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.419: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.419: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.419: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.420: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.420: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.420: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.420: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.420: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.420: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.421: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.421: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.421: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.421: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.421: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.421: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.422: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.422: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.422: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.422: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.422: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.422: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.423: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.423: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.423: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.423: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.423: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.423: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.424: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.424: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.424: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.424: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.424: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.424: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.425: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.425: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.425: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.425: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.425: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.425: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.426: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.426: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.426: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.426: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.426: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.426: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.427: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.427: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.427: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.427: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.427: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.427: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.428: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.428: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.428: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.428: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.428: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.428: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.429: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.429: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.429: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.429: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.429: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.429: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.430: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.430: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.430: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.430: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.430: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.430: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.431: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.431: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.431: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.431: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.431: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.431: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.432: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.432: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.432: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.432: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.432: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.432: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.433: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.433: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.433: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.433: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.433: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.433: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.434: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.434: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.434: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.434: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.434: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.434: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.435: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.435: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.435: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.435: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.435: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.435: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.435: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.435: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.436: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.436: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.436: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.436: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.436: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.436: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.437: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.437: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.437: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.437: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.437: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.437: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.438: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.438: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.438: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.438: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.438: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.438: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.439: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.439: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.439: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.439: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.440: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.440: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.440: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.440: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.440: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.440: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.441: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.441: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.441: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.441: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.441: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.441: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.442: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.442: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.442: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.442: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.442: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.442: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.443: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.443: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.443: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.443: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.443: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.443: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.444: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.444: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.444: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.444: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.444: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.444: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.444: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.444: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.445: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.445: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.445: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.445: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.445: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.445: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.446: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.446: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.446: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.446: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.446: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.446: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.447: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.447: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.447: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.447: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.447: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.447: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.448: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.448: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.448: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.448: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.448: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.448: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.449: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.449: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.449: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.449: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.449: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.449: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.450: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.450: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.450: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.450: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.450: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.450: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.451: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.451: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.451: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.451: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.451: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.451: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.452: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.452: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.452: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.452: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.452: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.452: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.453: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.453: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.453: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.453: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.453: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.453: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.454: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.454: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.454: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.454: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.454: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.454: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.455: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.455: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.455: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.455: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.455: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.455: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.456: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.456: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.456: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.456: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.456: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.456: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.457: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.457: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.457: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.457: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.457: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.457: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.458: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.458: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.458: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.458: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.458: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.458: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.459: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.459: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.459: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.459: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.459: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.459: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.460: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.460: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.460: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.460: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.460: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.460: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.461: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.461: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.461: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.461: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.461: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.461: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.462: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.462: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.462: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.462: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.462: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.462: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.463: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.463: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.463: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.463: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.463: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.463: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.464: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.464: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.464: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.464: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.464: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.464: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.465: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.465: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.465: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.465: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.465: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.465: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.466: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.466: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.466: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.466: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.466: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.466: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.467: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.467: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.467: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.467: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.467: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.467: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.468: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.468: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.468: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.468: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.468: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.468: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.469: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.469: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.469: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.469: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.469: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.469: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.470: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.470: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.470: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.470: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.470: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.470: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.471: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.471: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.471: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.471: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.471: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.471: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.472: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.472: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.472: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.472: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.472: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.472: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.473: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.473: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.473: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.473: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.473: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.473: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.473: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.473: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.474: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.474: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.474: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.474: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.474: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.474: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.475: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.475: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.475: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.475: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.475: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.475: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.476: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.476: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.476: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.476: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.476: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.476: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.477: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.477: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.477: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.477: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.477: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.477: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.478: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.478: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.478: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.478: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.478: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.478: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.479: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.479: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.479: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.479: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.479: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.479: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.480: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.480: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.480: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.480: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.480: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.480: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.481: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.481: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.481: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.481: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.481: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.481: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.482: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.482: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.482: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.482: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.482: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.482: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.483: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.483: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.483: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.483: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.483: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.483: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.483: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.483: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.484: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.484: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.484: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.484: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.484: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.484: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.485: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.485: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.485: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.485: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.485: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.485: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.486: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.486: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.486: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.486: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.486: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.486: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.487: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.487: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.487: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.487: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.487: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.487: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.487: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.488: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.488: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.488: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.488: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.488: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.489: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.489: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.489: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.489: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.489: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.489: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.490: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.490: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.490: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.490: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.490: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.490: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.491: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.491: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.491: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.491: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.491: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.491: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.492: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.492: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.492: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.492: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.492: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.492: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.492: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.492: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.493: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.493: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.493: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.493: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.493: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.493: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.494: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.494: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.494: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.494: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.494: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.494: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.495: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.495: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.495: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.495: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.495: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.495: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.496: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.496: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.496: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.496: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.496: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.496: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.497: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.497: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.497: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.497: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.497: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.497: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.498: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.498: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.498: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.498: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.498: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.498: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.499: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.499: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.499: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.499: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.499: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.499: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.500: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.500: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.500: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.500: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.500: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.500: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.500: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.500: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.501: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.501: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.501: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.501: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.501: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.501: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.502: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.502: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.502: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.502: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.502: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.502: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.503: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.503: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.503: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.503: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.503: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.503: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.504: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.504: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.504: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.504: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.504: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.504: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.505: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.505: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.505: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.505: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.505: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.505: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.506: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.506: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.506: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.506: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.506: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.506: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.507: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.507: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.507: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.507: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.507: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.507: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.508: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.508: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.508: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.508: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.508: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.508: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.509: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.509: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.509: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.509: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.509: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.509: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.510: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.510: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.510: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.510: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.510: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.510: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.511: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.511: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.511: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.511: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.511: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.511: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.512: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.512: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.512: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.512: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.512: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.512: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.513: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.513: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.513: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.513: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.513: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.513: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.514: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.514: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.514: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.514: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.514: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.514: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.515: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.515: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.515: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.515: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.515: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.515: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.516: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.516: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.516: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.516: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.516: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.516: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.517: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.517: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.517: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.517: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.517: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.517: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.518: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.518: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.518: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.518: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.518: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.518: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.519: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.519: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.519: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.519: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.519: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.519: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.520: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.520: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.520: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.520: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.520: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.520: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.520: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.520: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.521: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.521: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.521: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.521: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.521: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.521: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.522: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.522: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.522: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.522: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.522: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.522: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.523: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.523: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.523: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.523: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.523: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.523: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.524: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.524: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.524: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.524: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.524: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.524: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.525: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.525: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.525: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.525: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.525: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.525: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.525: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.525: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.526: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.526: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.526: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.526: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.526: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.526: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.527: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.527: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.527: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.527: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.527: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.527: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.528: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.528: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.528: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.528: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.528: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.528: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.529: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.529: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.529: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.529: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.529: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.529: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.530: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.530: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.530: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.530: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.530: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.530: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.531: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.531: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.531: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.531: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.531: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.531: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.532: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.532: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.532: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.532: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.532: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.532: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.533: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.533: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.533: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.533: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.533: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.533: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.534: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.534: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.534: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.534: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.534: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.534: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.535: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.535: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.535: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.535: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.535: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.535: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.536: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.536: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.536: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.536: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.536: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.536: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.537: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.537: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.537: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.537: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.537: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.537: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.538: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.538: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.538: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.538: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.538: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.538: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.539: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.539: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.539: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.539: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.539: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.539: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.540: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.540: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.540: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.540: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.540: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.541: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.541: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.541: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.541: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.541: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.541: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.542: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.542: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.542: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.542: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.542: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.543: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.543: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.543: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.543: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.543: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.543: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.544: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.544: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.544: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.544: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.544: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.544: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.544: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.545: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.545: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.545: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.545: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.545: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.545: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.545: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.546: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.546: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.546: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.546: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.546: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.546: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.547: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.547: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.547: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.547: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.547: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.547: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.548: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.548: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.548: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.548: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.548: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.548: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.549: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.549: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.549: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.549: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.549: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.549: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.550: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.550: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.550: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.550: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.550: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.550: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.551: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.551: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.551: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.551: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.551: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.551: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.552: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.552: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.552: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.552: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.552: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.552: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.553: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.553: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.553: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.553: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.553: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.553: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.554: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.554: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.554: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.554: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.554: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.554: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.555: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.555: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.555: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.555: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.555: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.555: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.556: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.556: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.556: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.556: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.556: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.556: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.557: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.557: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.557: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.557: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.557: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.557: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.558: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.558: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.558: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.558: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.558: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.558: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.559: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.559: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.559: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.559: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.559: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.559: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.560: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.560: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.560: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.560: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.560: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.560: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.561: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.561: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.561: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.561: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.561: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.561: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.562: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.562: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.562: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.562: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.562: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.562: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.563: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.563: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.563: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.563: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.563: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.563: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.563: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.564: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.564: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.564: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.564: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.564: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.565: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.565: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.565: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.565: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.565: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.565: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.566: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.566: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.566: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.566: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.566: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.566: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.567: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.567: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.567: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.567: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.567: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.567: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.567: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.568: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.568: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.568: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.568: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.568: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.569: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.569: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.569: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.569: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.569: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.569: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.570: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.570: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.570: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.570: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.570: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.570: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.571: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.571: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.571: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.571: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.571: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.571: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.572: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.572: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.572: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.572: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.572: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.572: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.572: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.573: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.573: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.573: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.573: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.573: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.573: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.573: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.574: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.574: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.574: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.574: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.574: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.574: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.575: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.575: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.575: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.575: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.575: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.575: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.576: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.576: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.576: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.576: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.576: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.576: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.576: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.577: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.577: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.577: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.577: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.577: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.577: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.577: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.577: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.578: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.578: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.578: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.578: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.578: variance_after = 20 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.578: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.578: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.579: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.579: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.579: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.579: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.580: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.580: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.580: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.580: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.581: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.581: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.581: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.581: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.581: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.581: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.582: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.582: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.582: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.582: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.582: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.582: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.583: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.583: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.583: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.583: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.583: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.583: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.584: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.584: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.584: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.584: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.584: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.584: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.585: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.585: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.585: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.585: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.585: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.585: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.586: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.586: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.586: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.586: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.586: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.586: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.587: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.587: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.587: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.587: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.587: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.587: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.588: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.588: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.588: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.588: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.588: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.588: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.589: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.589: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.589: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.589: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.589: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.589: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.590: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.590: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.590: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.590: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.590: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.590: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.591: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.591: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.591: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.591: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.591: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.591: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.592: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.592: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.592: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.592: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.592: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.592: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.593: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.593: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.593: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.593: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.593: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.593: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.594: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.594: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.594: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.594: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.594: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.594: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.595: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.595: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.595: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.595: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.595: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.595: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.595: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.595: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.596: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.596: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.596: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.596: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.596: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.596: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.597: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.597: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.597: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.597: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.597: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.597: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.598: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.598: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.598: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.598: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.598: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.598: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.599: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.599: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.599: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.599: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.599: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.599: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.600: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.600: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.600: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.600: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.600: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.600: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.601: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.601: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.601: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.601: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.601: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.601: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.602: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.602: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.602: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.602: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.602: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.602: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.603: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.603: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.603: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.603: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.603: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.603: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.603: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.603: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.604: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.604: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.604: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.604: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.604: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.605: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.605: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.605: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.605: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.605: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.605: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.606: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.606: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.606: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.606: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.606: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.606: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.607: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.607: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.607: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.607: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.607: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.607: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.608: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.608: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.608: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.608: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.608: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.608: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.609: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.609: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.609: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.609: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.609: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.609: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.610: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.610: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.610: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.610: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.610: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.610: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.611: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.611: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.611: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.611: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.611: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.611: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.612: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.612: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.612: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.612: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.612: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.612: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.613: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.613: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.613: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.613: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.613: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.613: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.613: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.613: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.614: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.614: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.614: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.614: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.614: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.614: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.615: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.615: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.615: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.615: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.615: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.615: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.616: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.616: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.616: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.616: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.616: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.616: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.617: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.617: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.617: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.617: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.617: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.617: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.618: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.618: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.618: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.618: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.618: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.618: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.619: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.619: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.619: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.619: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.619: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.619: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.620: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.620: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.620: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.620: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.620: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.620: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.621: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.621: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.621: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.621: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.621: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.621: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.622: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.622: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.622: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.622: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.622: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.622: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.623: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.623: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.623: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.623: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.623: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.623: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.624: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.624: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.624: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.624: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.624: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.624: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.624: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.624: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.625: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.625: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.625: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.625: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.625: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.625: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.626: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.626: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.626: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.626: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.626: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.626: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.627: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.627: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.627: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.627: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.627: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.627: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.628: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.628: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.628: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.628: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.628: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.628: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.629: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.629: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.629: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.629: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.629: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.629: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.630: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.630: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.630: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.630: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.630: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.630: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.631: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.631: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.631: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.631: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.631: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.632: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.632: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.632: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.632: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.632: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.633: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.633: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.633: variance_after = 18 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.633: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.633: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.633: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.633: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.634: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.634: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.634: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.634: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.634: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.634: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.635: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.635: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.635: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.635: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.635: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.635: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.636: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.636: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.636: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.636: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.636: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.636: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.637: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.637: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.637: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.637: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.637: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.637: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.638: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.638: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.638: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.638: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.638: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.638: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.639: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.639: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.639: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.639: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.639: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.639: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.640: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.640: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.640: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.640: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.640: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.640: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.641: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.641: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.641: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.641: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.641: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.641: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.642: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.642: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.642: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.642: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.642: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.642: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.643: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.643: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.643: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.643: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.643: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.643: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.643: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.644: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.644: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.644: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.644: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.644: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.645: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.645: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.645: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.645: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.645: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.645: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.645: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.645: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.646: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.646: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.646: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.646: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.646: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.646: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.647: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.647: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.647: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.647: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.647: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.647: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.647: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.648: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.648: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.648: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.648: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.648: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.649: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.649: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.649: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.649: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.649: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.649: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.650: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.650: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.650: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.650: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.650: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.650: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.651: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.651: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.651: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.651: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.651: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.651: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.652: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.652: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.652: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.652: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.652: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.652: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.653: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.653: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.653: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.653: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.653: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.653: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.654: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.654: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.654: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.654: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.654: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.654: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.654: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.654: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.655: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.655: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.655: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.655: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.655: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.655: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.656: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.656: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.656: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.656: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.656: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.656: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.657: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.657: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.657: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.657: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.657: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.657: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.658: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.658: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.658: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.658: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.658: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.658: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.659: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.659: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.659: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.659: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.659: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.659: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.660: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.660: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.660: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.660: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.660: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.660: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.661: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.661: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.661: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.661: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.661: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.661: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.662: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.662: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.662: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.662: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.662: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.662: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.663: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.663: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.663: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.663: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.663: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.663: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.664: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.664: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.664: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.664: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.664: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.664: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.665: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.665: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.665: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.665: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.665: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.665: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.666: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.666: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.666: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.666: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.666: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.666: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.667: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.667: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.667: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.667: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.667: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.667: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.668: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.668: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.668: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.668: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.668: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.668: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.669: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.669: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.669: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.669: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.669: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.669: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.670: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.670: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.670: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.670: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.670: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.670: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.671: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.671: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.671: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.671: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.671: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.671: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.672: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.672: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.672: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.672: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.672: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.672: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.673: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.673: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.673: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.673: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.673: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.673: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.674: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.674: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.674: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.674: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.674: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.674: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.675: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.675: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.676: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.676: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.676: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.676: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.676: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.676: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.677: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.677: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.677: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.677: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.677: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.677: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.678: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.678: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.678: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.678: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.678: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.678: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.679: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.679: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.679: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.679: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.679: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.679: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.680: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.680: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.680: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.680: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.680: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.680: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.681: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.681: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.681: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.681: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.681: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.681: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.682: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.682: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.682: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.682: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.682: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.682: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.683: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.683: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.683: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.683: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.683: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.683: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.683: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.683: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.684: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.684: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.684: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.684: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.684: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.684: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.685: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.685: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.685: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.685: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.685: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.685: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.686: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.686: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.686: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.686: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.686: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.686: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.686: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.687: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.687: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.687: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.687: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.687: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.688: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.688: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.688: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.688: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.688: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.689: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.689: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.689: variance_after = 18 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.689: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.689: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.689: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.689: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.690: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.690: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.690: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.690: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.690: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.690: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.691: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.691: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.691: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.691: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.691: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.691: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.692: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.692: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.692: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.692: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.692: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.692: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.693: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.693: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.693: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.693: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.693: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.693: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.694: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.694: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.694: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.694: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.694: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.694: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.695: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.695: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.695: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.695: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.695: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.695: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.696: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.696: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.696: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.696: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.696: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.696: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.697: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.697: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.697: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.697: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.697: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.697: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.698: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.698: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.698: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.698: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.698: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.698: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.699: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.699: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.699: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.699: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.699: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.699: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.700: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.700: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.700: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.700: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.700: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.700: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.701: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.701: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.701: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.701: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.701: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.701: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.702: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.702: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.702: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.702: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.702: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.702: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.703: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.703: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.703: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.703: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.703: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.703: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.704: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.704: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.704: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.704: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.704: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.704: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.705: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.705: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.705: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.705: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.705: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.705: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.706: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.706: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.706: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.706: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.706: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.706: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.706: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.706: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.707: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.707: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.707: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.707: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.707: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.707: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.708: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.708: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.708: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.708: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.708: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.708: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.709: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.709: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.709: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.709: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.709: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.709: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.710: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.710: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.710: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.710: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.710: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.710: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.710: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.710: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.711: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.711: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.711: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.711: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.711: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.712: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.712: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.712: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.712: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.712: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.712: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.713: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.713: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.713: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.713: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.713: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.713: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.714: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.714: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.714: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.714: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.714: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.714: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.715: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.715: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.715: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.715: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.715: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.715: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.716: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.716: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.716: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.716: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.716: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.716: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.717: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.717: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.717: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.717: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.717: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.717: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.718: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.718: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.718: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.718: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.718: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.718: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.719: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.719: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.719: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.719: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.719: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.719: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.719: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.719: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.720: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.720: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.720: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.720: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.720: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.720: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.721: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.721: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.721: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.721: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.721: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.721: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.722: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.722: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.722: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.722: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.722: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.722: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.723: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.723: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.723: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.723: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.723: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.723: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.724: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.724: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.724: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.724: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.724: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.724: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.725: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.725: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.725: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.725: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.725: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.725: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.726: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.726: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.726: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.726: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.726: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.726: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.727: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.727: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.727: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.727: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.727: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.727: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.727: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.728: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.728: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.728: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.728: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.728: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.729: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.729: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.729: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.729: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.729: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.729: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.730: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.730: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.730: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.730: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.730: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.730: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.731: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.731: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.731: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.731: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.731: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.731: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.732: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.732: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.732: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.732: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.732: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.732: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.733: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.733: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.733: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.733: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.733: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.733: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.734: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.734: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.734: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.734: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.734: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.734: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.735: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.735: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.735: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.735: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.735: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.735: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.736: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.736: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.736: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.736: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.736: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.736: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.737: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.737: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.737: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.737: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.737: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.737: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.738: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.738: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.738: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.738: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.738: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.738: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.739: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.739: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.739: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.739: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.739: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.739: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.740: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.740: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.740: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.740: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.740: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.740: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.741: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.741: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.741: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.741: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.741: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.741: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.742: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.742: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.742: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.742: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.742: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.742: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.743: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.743: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.743: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.743: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.743: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.743: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.744: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.744: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.744: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.745: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.745: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.745: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.745: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.745: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.746: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.746: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.746: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.746: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.746: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.746: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.747: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.747: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.747: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.747: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.747: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.747: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.748: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.748: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.748: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.748: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.748: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.748: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.749: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.749: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.749: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.749: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.749: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.749: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.750: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.750: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.750: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.750: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.750: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.750: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.751: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.751: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.751: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.751: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.751: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.751: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.752: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.752: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.752: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.752: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.752: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.752: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.753: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.753: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.753: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.753: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.753: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.753: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.754: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.754: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.754: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.754: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.754: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.754: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.754: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.755: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.755: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.755: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.755: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.755: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.755: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.755: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.756: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.756: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.756: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.756: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.756: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.756: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.757: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.757: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.757: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.757: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.757: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.757: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.758: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.758: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.758: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.758: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.758: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.758: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.759: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.759: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.759: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.759: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.759: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.759: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.760: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.760: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.760: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.760: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.760: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.760: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.761: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.761: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.761: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.761: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.761: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.761: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.762: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.762: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.762: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.762: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.762: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.762: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.763: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.763: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.763: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.763: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.763: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.763: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.764: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.764: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.764: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.764: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.764: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.764: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.765: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.765: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.765: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.765: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.765: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.765: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.765: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.765: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.766: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.766: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.766: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.766: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.766: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.766: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.767: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.767: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.767: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.767: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.767: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.767: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.768: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.768: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.768: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.768: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.768: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.768: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.769: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.769: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.769: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.769: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.769: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.769: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.770: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.770: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.770: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.770: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.770: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.770: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.771: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.771: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.771: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.771: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.771: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.771: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.772: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.772: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.772: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.772: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.772: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.772: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.773: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.773: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.773: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.773: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.773: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.773: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.773: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.774: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.774: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.774: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.774: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.774: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.775: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.775: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.775: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.775: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.775: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.776: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.776: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.776: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.776: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.776: variance_after = 18 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.776: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.776: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.777: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.777: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.777: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.777: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.777: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.777: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.778: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.778: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.778: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.778: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.778: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.778: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.779: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.779: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.779: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.779: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.779: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.779: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.779: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.780: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.780: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.780: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.780: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.780: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.780: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.780: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.781: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.781: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.781: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.781: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.781: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.781: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.782: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.782: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.782: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.782: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.782: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.782: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.783: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.783: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.783: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.783: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.783: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.783: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.784: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.784: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.784: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.784: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.784: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.784: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.785: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.785: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.785: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.785: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.785: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.785: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.786: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.786: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.786: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.786: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.786: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.786: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.786: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.786: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.787: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.787: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.787: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.787: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.787: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.787: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.787: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.787: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.788: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.788: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.788: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.788: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.788: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.788: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.789: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.789: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.789: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.789: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.789: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.789: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.790: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.790: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.790: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.790: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.790: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.790: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.791: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.791: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.791: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.791: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.791: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.791: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.791: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.791: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.792: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.792: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.792: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.792: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.793: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.793: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.793: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.793: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.793: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.793: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.794: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.794: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.794: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.794: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.794: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.794: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.794: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.794: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.795: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.795: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.795: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.795: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.795: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.795: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.796: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.796: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.796: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.796: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.796: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.796: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.797: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.797: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.797: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.797: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.797: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.797: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.798: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.798: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.798: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.798: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.798: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.798: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.799: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.799: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.799: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.799: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.799: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.799: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.800: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.800: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.800: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.800: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.800: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.800: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.801: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.801: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.801: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.801: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.801: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.801: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.802: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.802: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.802: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.802: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.802: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.802: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.802: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.803: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.803: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.803: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.803: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.803: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.804: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.804: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.804: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.804: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.804: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.804: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.805: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.805: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.805: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.805: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.805: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.805: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.806: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.806: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.806: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.806: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.806: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.806: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.807: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.807: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.807: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.807: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.807: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.807: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.808: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.808: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.808: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.808: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.808: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.808: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.808: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.808: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.809: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.809: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.809: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.809: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.809: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.809: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.810: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.810: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.810: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.810: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.810: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.810: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.811: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.811: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.811: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.811: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.811: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.811: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.812: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.812: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.812: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.812: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.812: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.812: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.813: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.813: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.813: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.813: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.813: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.813: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.814: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.814: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.814: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.814: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.814: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.814: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.815: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.815: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.815: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.815: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.815: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.815: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.816: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.816: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.816: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.816: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.816: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.816: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.817: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.817: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.817: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.817: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.817: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.817: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.818: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.818: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.818: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.818: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.818: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.818: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.819: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.819: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.819: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.819: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.819: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.819: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.819: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.819: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.820: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.820: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.820: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.820: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.820: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.820: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.821: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.821: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.821: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.821: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.821: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.821: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.822: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.822: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.822: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.822: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.822: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.822: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.823: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.823: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.823: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.823: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.823: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.823: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.824: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.824: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.824: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.824: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.824: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.824: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.825: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.825: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.825: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.825: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.825: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.825: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.826: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.826: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.826: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.826: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.826: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.826: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.827: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.827: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.827: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.827: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.827: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.827: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.828: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.828: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.828: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.828: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.828: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.828: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.829: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.829: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.829: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.829: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.829: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.829: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.829: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.829: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.830: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.830: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.830: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.830: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.830: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.830: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.831: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.831: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.831: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.831: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.831: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.831: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.832: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.832: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.832: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.832: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.832: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.832: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.833: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.833: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.833: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.833: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.833: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.833: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.834: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.834: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.834: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.834: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.834: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.834: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.835: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.835: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.835: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.835: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.835: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.835: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.836: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.836: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.836: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.836: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.836: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.836: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.837: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.837: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.837: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.837: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.837: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.837: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.838: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.838: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.838: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.838: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.838: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.838: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.839: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.839: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.839: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.839: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.839: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.839: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.840: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.840: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.840: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.840: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.840: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.840: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.840: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.840: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.841: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.841: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.841: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.841: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.841: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.842: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.842: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.842: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.842: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.842: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.842: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.842: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.843: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.843: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.843: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.843: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.843: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.843: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.844: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.844: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.844: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.844: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.844: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.844: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.845: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.845: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.845: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.845: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.845: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.845: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.846: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.846: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.846: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.846: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.846: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.846: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.847: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.847: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.847: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.847: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.847: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.847: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.848: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.848: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.848: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.848: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.848: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.848: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.849: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.849: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.849: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.849: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.849: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.849: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.850: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.850: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.850: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.850: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.850: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.850: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.851: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.851: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.851: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.851: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.851: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.851: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.852: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.852: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.852: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.852: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.852: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.852: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.853: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.853: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.853: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.853: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.853: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.853: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.854: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.854: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.854: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.854: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.854: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.854: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.855: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.855: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.855: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.855: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.855: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.855: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.855: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.855: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.856: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.856: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.856: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.856: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.856: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.856: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.857: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.857: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.857: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.857: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.857: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.857: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.858: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.858: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.858: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.858: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.858: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.858: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.859: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.859: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.859: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.859: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.859: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.859: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.860: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.860: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.860: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.860: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.860: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.860: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.860: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.861: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.861: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.861: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.861: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.861: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.862: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.862: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.862: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.862: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.862: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.862: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.863: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.863: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.863: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.863: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.864: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.864: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.864: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.864: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.864: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.864: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.864: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.864: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.865: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.865: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.865: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.865: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.865: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.865: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.866: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.866: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.866: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.866: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.866: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.866: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.867: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.867: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.867: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.867: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.867: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.867: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.868: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.868: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.868: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.868: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.868: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.868: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.869: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.869: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.869: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.869: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.870: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.870: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.870: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.870: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.870: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.871: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.871: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.871: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.871: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.871: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.872: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.872: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.872: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.872: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.872: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.873: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.873: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.873: variance_after = 18 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.873: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.873: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.873: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.874: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.874: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.874: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.874: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.874: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.875: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.875: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.875: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.875: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.875: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.875: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.876: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.876: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.876: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.876: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.876: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.876: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.877: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.877: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.877: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.877: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.877: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.877: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.878: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.878: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.878: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.878: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.878: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.878: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.879: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.879: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.879: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.879: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.879: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.879: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.880: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.880: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.880: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.880: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.880: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.880: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.880: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.880: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.881: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.881: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.881: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.881: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.881: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.881: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.882: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.882: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.882: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.882: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.882: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.882: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.883: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.883: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.883: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.883: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.883: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.883: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.884: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.884: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.884: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.884: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.884: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.884: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.885: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.885: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.885: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.885: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.885: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.885: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.886: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.886: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.886: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.886: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.886: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.886: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.887: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.887: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.887: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.887: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.887: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.887: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.888: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.888: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.888: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.888: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.888: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.888: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.889: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.889: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.889: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.889: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.889: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.889: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.890: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.890: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.890: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.890: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.890: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.890: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.891: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.891: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.891: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.891: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.891: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.891: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.891: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.892: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.892: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.892: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.892: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.892: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.893: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.893: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.893: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.893: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.893: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.893: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.894: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.894: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.894: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.894: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.894: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.894: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.895: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.895: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.895: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.895: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.895: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.895: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.896: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.896: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.896: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.896: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.896: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.896: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.897: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.897: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.897: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.897: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.897: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.897: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.898: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.898: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.898: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.898: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.898: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.898: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.899: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.899: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.899: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.899: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.899: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.899: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.900: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.900: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.900: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.900: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.900: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.900: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.901: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.901: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.901: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.901: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.901: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.901: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.901: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.902: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.902: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.902: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.902: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.902: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.902: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.902: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.903: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.903: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.903: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.903: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.903: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.903: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.904: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.904: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.904: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.904: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.904: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.904: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.905: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.905: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.905: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.905: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.905: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.905: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.906: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.906: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.906: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.906: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.906: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.906: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.907: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.907: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.907: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.907: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.907: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.907: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.908: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.908: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.908: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.908: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.908: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.908: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.909: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.909: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.909: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.909: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.909: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.909: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.910: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.910: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.910: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.910: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.910: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.910: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.911: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.911: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.911: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.911: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.911: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.911: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.912: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.912: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.912: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.912: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.912: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.912: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.913: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.913: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.913: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.913: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.913: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.913: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.914: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.914: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.914: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.914: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.914: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.914: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.915: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.915: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.915: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.915: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.916: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.916: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.916: [vfs7552] CAPTURE_NUM_STATES entering state 2 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.916: [vfs7552] REQUEST CHUNK entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.916: Sending vfs7552_read_image_chunk 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.917: [vfs7552] REQUEST CHUNK completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.917: [vfs7552] CAPTURE_NUM_STATES entering state 3 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.917: [vfs7552] CAPTURE_NUM_STATES entering state 4 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.917: Cleaning image 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.917: variance_after = 17 190s 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.917: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.917: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.918: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.918: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.918: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.918: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.919: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.919: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.919: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.919: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.919: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.919: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.919: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.919: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.920: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.920: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.920: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.920: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.920: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.920: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.921: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.921: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.921: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.921: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.921: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.921: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.922: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.922: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.922: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.922: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.922: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.922: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.923: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.923: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.923: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.923: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.923: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.923: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.923: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.924: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.924: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.924: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.924: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.924: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.925: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.925: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.925: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.925: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.925: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.925: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.925: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.925: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.926: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.926: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.926: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.926: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.926: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.926: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.927: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.927: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.927: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.927: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.927: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.927: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.928: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.928: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.928: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.928: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.928: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.928: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.929: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.929: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.929: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.929: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.929: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.929: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.930: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.930: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.930: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.930: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.930: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.930: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.931: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.931: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.931: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.931: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.931: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.931: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.932: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.932: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.932: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.932: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.932: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.932: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.933: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.933: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.933: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.933: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.933: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.933: Sending vfs7552_is_image_ready 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.934: [vfs7552] QUERY DATA READY entering state 1 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.934: Receiving 64 bytes 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.934: Got 6 bytes out of 64 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.934: [vfs7552] QUERY DATA READY completed successfully 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 190s (process:4246): libfprint-SSM-DEBUG: 20:26:38.934: [vfs7552] QUERY DATA READY entering state 0 190s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.934: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.934: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.934: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.935: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.935: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.935: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.935: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.935: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.935: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.936: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.936: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.936: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.936: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.936: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.936: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.937: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.937: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.937: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.937: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.937: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.937: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.938: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.938: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.938: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.938: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.938: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.938: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.939: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.939: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.939: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.939: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.939: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.939: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.940: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.940: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.940: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.940: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.940: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.940: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.941: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.941: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.941: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.941: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.941: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.941: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.942: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.942: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.942: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.942: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.942: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.942: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.942: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.942: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.943: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.943: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.943: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.943: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.943: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.944: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.944: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.944: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.944: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.944: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.944: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.945: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.945: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.945: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.945: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.946: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.946: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.946: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.946: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.946: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.947: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.947: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.947: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.947: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.947: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.947: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.948: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.948: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.948: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.948: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.948: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.948: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.949: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.949: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.949: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.949: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.949: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.949: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.950: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.950: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.950: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.950: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.950: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.950: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.951: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.951: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.951: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.951: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.951: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.951: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.952: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.952: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.952: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.952: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.952: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.952: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.953: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.953: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.953: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.953: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.953: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.953: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.954: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.954: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.954: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.954: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.954: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.954: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.954: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.954: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.955: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.955: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.955: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.955: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.955: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.955: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.956: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.956: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.956: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.956: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.956: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.956: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.957: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.957: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.957: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.957: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.957: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.957: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.958: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.958: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.958: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.958: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.958: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.958: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.958: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.959: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.959: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.959: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.959: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.959: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.960: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.960: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.960: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.960: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.960: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.961: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.961: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.961: variance_after = 16 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.961: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.961: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.961: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.961: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.962: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.962: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.962: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.962: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.962: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.962: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.963: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.963: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.963: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.963: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.963: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.963: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.964: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.964: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.964: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.964: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.964: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.964: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.965: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.965: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.965: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.965: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.965: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.965: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.966: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.966: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.966: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.966: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.966: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.966: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.967: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.967: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.967: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.967: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.967: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.967: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.967: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.968: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.968: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.968: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.968: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.968: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.969: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.969: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.969: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.969: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.969: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.969: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.970: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.970: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.970: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.970: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.970: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.970: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.971: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.971: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.971: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.971: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.971: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.971: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.972: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.972: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.972: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.972: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.972: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.972: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.973: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.973: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.973: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.973: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.973: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.973: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.974: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.974: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.974: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.974: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.974: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.974: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.975: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.975: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.975: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.975: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.975: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.975: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.976: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.976: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.976: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.976: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.976: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.976: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.977: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.977: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.977: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.977: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.977: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.977: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.978: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.978: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.978: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.978: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.978: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.978: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.979: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.979: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.979: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.979: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.979: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.979: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.980: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.980: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.980: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.980: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.980: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.980: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.981: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.981: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.981: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.981: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.981: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.981: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.982: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.982: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.982: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.982: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.982: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.982: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.982: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.982: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.983: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.983: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.983: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.983: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.983: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.983: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.984: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.984: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.984: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.984: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.984: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.984: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.985: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.985: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.985: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.985: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.985: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.985: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.986: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.986: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.986: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.986: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.986: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.986: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.987: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.987: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.987: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.987: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.987: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.987: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.988: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.988: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.988: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.988: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.988: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.988: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.989: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.989: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.989: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.989: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.989: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.989: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.990: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.990: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.990: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.990: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.990: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.990: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.991: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.991: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.991: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.991: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.991: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.991: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.992: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.992: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.992: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.992: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.992: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.992: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.993: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.993: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.993: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.993: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.993: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.993: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.994: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.994: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.994: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.994: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.994: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.994: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.994: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.994: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.995: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.995: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.995: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.995: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.996: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.996: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.996: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.996: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.996: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.996: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.997: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.997: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.997: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.997: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.997: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.997: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.998: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.998: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.998: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.998: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.998: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.998: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.999: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.999: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.999: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.999: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:38.999: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:38.999: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.000: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.000: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.000: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.000: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.000: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.000: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.001: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.001: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.001: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.001: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.001: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.001: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.002: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.002: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.002: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.002: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.002: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.002: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.002: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.003: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.003: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.003: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.003: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.003: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.004: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.004: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.004: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.004: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.004: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.005: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.005: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.005: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.005: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.005: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.005: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.005: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.006: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.006: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.006: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.006: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.006: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.006: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.007: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.007: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.007: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.007: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.007: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.007: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.008: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.008: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.008: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.008: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.008: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.008: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.009: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.009: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.009: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.009: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.009: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.009: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.009: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.010: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.010: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.010: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.010: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.010: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.010: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.010: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.011: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.011: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.011: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.011: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.011: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.011: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.012: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.012: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.012: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.012: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.012: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.012: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.013: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.013: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.013: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.013: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.013: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.013: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.014: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.014: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.014: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.014: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.014: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.014: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.015: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.015: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.015: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.015: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.015: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.015: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.016: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.016: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.016: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.016: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.016: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.016: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.016: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.017: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.017: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.017: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.017: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.017: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.018: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.018: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.018: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.018: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.018: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.018: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.019: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.019: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.019: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.019: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.019: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.019: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.020: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.020: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.020: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.020: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.020: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.020: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.021: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.021: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.021: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.021: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.021: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.021: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.022: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.022: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.022: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.022: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.022: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.022: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.023: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.023: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.023: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.023: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.023: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.023: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.023: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.023: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.024: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.024: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.024: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.024: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.024: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.024: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.025: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.025: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.025: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.025: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.025: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.025: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.026: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.026: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.026: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.026: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.026: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.026: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.027: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.027: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.027: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.027: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.027: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.027: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.028: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.028: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.028: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.028: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.028: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.028: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.029: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.029: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.029: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.029: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.029: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.029: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.030: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.030: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.030: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.030: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.030: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.030: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.031: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.031: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.031: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.031: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.031: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.031: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.032: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.032: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.032: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.032: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.032: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.032: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.033: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.033: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.033: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.033: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.033: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.033: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.034: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.034: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.034: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.034: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.034: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.034: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.035: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.035: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.035: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.035: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.035: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.035: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.036: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.036: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.036: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.036: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.036: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.036: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.036: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.037: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.037: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.037: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.037: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.037: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.037: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.037: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.038: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.038: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.038: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.038: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.038: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.038: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.039: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.039: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.039: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.039: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.039: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.039: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.040: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.040: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.040: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.040: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.040: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.040: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.041: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.041: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.041: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.041: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.041: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.041: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.042: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.042: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.042: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.042: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.042: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.042: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.043: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.043: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.043: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.043: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.043: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.043: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.044: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.044: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.044: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.044: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.044: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.044: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.045: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.045: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.045: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.045: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.045: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.045: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.046: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.046: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.046: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.046: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.046: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.046: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.047: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.047: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.047: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.047: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.047: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.047: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.048: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.048: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.048: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.048: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.048: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.048: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.049: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.049: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.049: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.049: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.049: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.049: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.050: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.050: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.050: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.050: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.050: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.050: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.050: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.050: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.050: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.051: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.051: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.051: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.051: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.051: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.052: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.052: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.052: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.052: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.052: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.053: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.053: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.053: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.053: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.053: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.053: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.053: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.054: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.054: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.054: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.054: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.054: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.054: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.055: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.055: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.055: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.055: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.055: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.055: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.056: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.056: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.056: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.056: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.056: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.056: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.056: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.057: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.057: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.057: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.057: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.057: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.058: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.058: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.058: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.058: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.058: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.058: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.059: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.059: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.059: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.059: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.059: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.059: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.060: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.060: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.060: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.060: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.060: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.060: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.061: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.061: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.061: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.061: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.061: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.061: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.062: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.062: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.062: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.062: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.062: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.062: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.063: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.063: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.063: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.063: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.063: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.063: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.064: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.064: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.064: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.064: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.064: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.064: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.065: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.065: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.065: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.065: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.065: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.065: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.066: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.066: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.066: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.066: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.066: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.066: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.067: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.067: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.067: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.067: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.067: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.067: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.067: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.067: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.068: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.068: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.068: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.068: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.068: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.068: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.069: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.069: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.069: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.069: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.069: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.069: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.070: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.070: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.070: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.070: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.070: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.070: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.071: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.071: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.071: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.071: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.071: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.071: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.071: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.072: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.072: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.072: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.072: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.072: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.073: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.073: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.073: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.073: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.073: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.073: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.074: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.074: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.074: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.074: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.074: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.074: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.075: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.075: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.075: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.075: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.075: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.075: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.076: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.076: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.076: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.076: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.076: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.076: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.077: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.077: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.077: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.077: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.077: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.077: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.077: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.077: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.078: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.078: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.078: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.078: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.078: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.078: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.079: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.079: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.079: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.079: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.079: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.079: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.080: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.080: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.080: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.080: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.080: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.080: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.081: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.081: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.081: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.081: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.081: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.081: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.081: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.082: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.082: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.082: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.082: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.082: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.083: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.083: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.083: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.083: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.083: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.083: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.084: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.084: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.084: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.084: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.084: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.084: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.085: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.085: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.085: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.085: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.085: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.085: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.086: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.086: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.086: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.086: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.086: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.086: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.087: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.087: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.087: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.087: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.087: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.087: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.088: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.088: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.088: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.088: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.088: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.088: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.088: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.088: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.089: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.089: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.089: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.089: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.089: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.089: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.090: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.090: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.090: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.090: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.090: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.090: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.091: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.091: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.091: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.091: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.091: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.091: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.092: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.092: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.092: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.092: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.092: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.092: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.093: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.093: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.093: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.093: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.093: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.093: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.093: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.093: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.094: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.094: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.094: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.094: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.094: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.095: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.095: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.095: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.095: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.095: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.095: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.096: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.096: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.096: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.096: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.096: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.096: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.097: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.097: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.097: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.097: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.097: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.097: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.098: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.098: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.098: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.098: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.098: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.098: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.098: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.098: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.099: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.099: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.099: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.099: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.099: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.099: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.100: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.100: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.100: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.100: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.100: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.100: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.101: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.101: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.101: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.101: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.101: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.101: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.102: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.102: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.102: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.102: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.102: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.102: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.103: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.103: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.103: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.103: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.103: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.103: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.104: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.104: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.104: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.104: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.104: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.104: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.105: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.105: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.105: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.105: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.105: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.105: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.106: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.106: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.106: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.106: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.106: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.106: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.106: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.107: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.107: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.107: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.107: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.107: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.108: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.108: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.108: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.108: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.108: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.109: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.109: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.109: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.109: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.109: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.109: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.109: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.110: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.110: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.110: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.110: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.110: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.110: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.111: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.111: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.111: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.111: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.111: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.111: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.112: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.112: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.112: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.112: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.112: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.112: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.112: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.112: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.113: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.113: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.113: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.113: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.113: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.113: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.114: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.114: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.114: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.114: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.114: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.114: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.115: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.115: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.115: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.115: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.115: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.115: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.116: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.116: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.116: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.116: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.116: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.116: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.117: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.117: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.117: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.117: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.117: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.117: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.118: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.118: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.118: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.118: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.118: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.118: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.118: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.119: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.119: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.119: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.119: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.119: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.120: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.120: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.120: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.120: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.120: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.120: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.121: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.121: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.121: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.121: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.121: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.121: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.122: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.122: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.122: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.122: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.122: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.122: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.122: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.122: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.123: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.123: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.123: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.123: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.123: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.123: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.124: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.124: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.124: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.124: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.124: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.124: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.125: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.125: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.125: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.125: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.125: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.125: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.126: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.126: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.126: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.126: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.126: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.126: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.127: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.127: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.127: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.127: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.127: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.127: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.128: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.128: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.128: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.128: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.129: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.129: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.129: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.129: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.129: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.129: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.130: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.130: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.130: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.130: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.130: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.130: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.130: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.131: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.131: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.131: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.131: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.131: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.131: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.131: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.132: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.132: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.132: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.132: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.132: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.132: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.133: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.133: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.133: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.133: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.133: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.133: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.134: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.134: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.134: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.134: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.134: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.134: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.135: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.135: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.135: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.135: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.135: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.135: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.136: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.136: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.136: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.136: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.136: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.136: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.137: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.137: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.137: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.137: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.137: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.137: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.138: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.138: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.138: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.138: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.138: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.138: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.139: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.139: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.139: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.139: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.139: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.139: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.140: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.140: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.140: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.140: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.140: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.140: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.141: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.141: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.141: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.141: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.141: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.141: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.142: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.142: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.142: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.142: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.142: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.142: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.143: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.143: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.143: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.143: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.143: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.143: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.143: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.143: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.144: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.144: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.144: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.144: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.144: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.144: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.145: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.145: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.145: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.145: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.145: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.145: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.146: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.146: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.146: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.146: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.146: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.146: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.147: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.147: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.147: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.147: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.147: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.147: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.148: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.148: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.148: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.148: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.148: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.148: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.149: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.149: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.149: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.149: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.149: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.149: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.150: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.150: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.150: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.150: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.150: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.150: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.151: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.151: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.151: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.151: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.151: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.151: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.152: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.152: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.152: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.152: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.152: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.152: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.152: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.152: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.153: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.153: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.153: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.153: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.153: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.153: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.154: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.154: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.154: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.154: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.154: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.154: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.155: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.155: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.155: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.155: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.155: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.155: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.156: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.156: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.156: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.156: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.156: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.156: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.157: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.157: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.157: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.157: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.157: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.157: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.158: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.158: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.158: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.158: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.158: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.158: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.159: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.159: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.159: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.159: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.159: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.159: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.159: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.160: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.160: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.160: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.160: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.160: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.161: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.161: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.161: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.161: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.161: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.161: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.162: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.162: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.162: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.162: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.162: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.162: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.163: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.163: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.163: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.163: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.163: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.163: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.164: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.164: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.164: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.164: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.164: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.164: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.164: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.164: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.165: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.165: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.165: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.165: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.165: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.165: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.166: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.166: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.166: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.166: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.166: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.166: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.167: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.167: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.167: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.167: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.167: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.167: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.168: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.168: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.168: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.168: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.168: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.168: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.169: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.169: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.169: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.169: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.169: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.169: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.170: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.170: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.170: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.170: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.170: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.170: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.171: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.171: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.171: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.171: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.171: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.171: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.172: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.172: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.172: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.172: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.172: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.172: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.173: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.173: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.173: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.173: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.173: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.173: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.173: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.174: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.174: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.174: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.174: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.174: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.174: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.174: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.175: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.175: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.175: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.175: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.175: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.175: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.176: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.176: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.176: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.176: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.176: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.176: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.177: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.177: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.177: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.177: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.177: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.177: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.178: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.178: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.178: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.178: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.178: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.178: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.179: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.179: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.179: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.179: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.179: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.179: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.179: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.180: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.180: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.180: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.180: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.180: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.181: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.181: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.181: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.181: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.181: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.181: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.182: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.182: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.182: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.182: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.182: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.182: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.183: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.183: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.183: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.183: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.183: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.183: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.184: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.184: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.184: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.184: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.184: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.184: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.185: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.185: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.185: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.185: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.185: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.185: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.186: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.186: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.186: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.186: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.186: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.186: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.187: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.187: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.188: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.188: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.188: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.188: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.188: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.188: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.189: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.189: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.189: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.189: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.189: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.189: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.190: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.190: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.190: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.190: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.190: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.190: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.191: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.191: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.191: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.191: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.191: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.191: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.192: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.192: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.192: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.192: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.192: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.192: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.192: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.193: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.193: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.193: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.193: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.193: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.194: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.194: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.194: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.194: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.194: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.194: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.194: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.194: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.195: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.195: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.195: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.195: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.195: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.195: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.196: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.196: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.196: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.196: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.196: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.196: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.197: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.197: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.197: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.197: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.197: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.197: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.198: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.198: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.198: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.198: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.198: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.198: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.199: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.199: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.199: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.199: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.199: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.199: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.200: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.200: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.200: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.200: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.200: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.200: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.201: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.201: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.201: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.201: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.201: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.201: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.202: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.202: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.202: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.202: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.202: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.202: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.203: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.203: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.203: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.203: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.203: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.203: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.203: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.203: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.204: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.204: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.204: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.204: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.204: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.204: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.205: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.205: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.205: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.205: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.205: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.205: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.206: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.206: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.206: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.206: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.206: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.206: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.207: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.207: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.207: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.207: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.207: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.207: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.208: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.208: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.209: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.209: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.209: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.209: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.209: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.209: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.210: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.210: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.210: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.210: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.210: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.210: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.211: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.211: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.211: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.211: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.211: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.211: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.212: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.212: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.212: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.212: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.212: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.212: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.213: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.213: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.213: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.213: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.213: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.213: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.214: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.214: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.214: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.214: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.214: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.214: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.215: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.215: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.215: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.215: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.215: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.215: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.216: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.216: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.216: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.216: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.216: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.216: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.217: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.217: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.217: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.217: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.217: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.217: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.217: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.218: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.218: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.218: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.218: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.218: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.218: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.218: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.219: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.219: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.219: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.219: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.219: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.219: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.220: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.220: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.220: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.220: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.221: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.221: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.221: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.221: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.221: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.221: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.221: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.221: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.222: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.222: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.222: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.222: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.222: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.222: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.223: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.223: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.223: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.223: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.223: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.223: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.224: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.224: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.224: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.224: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.224: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.224: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.225: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.225: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.225: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.225: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.225: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.225: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.226: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.226: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.226: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.226: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.226: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.226: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.227: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.227: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.227: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.227: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.227: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.227: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.228: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.228: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.228: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.228: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.228: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.228: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.229: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.229: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.229: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.229: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.229: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.229: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.230: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.230: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.230: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.230: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.230: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.230: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.231: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.231: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.231: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.231: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.231: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.231: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.232: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.232: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.232: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.232: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.232: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.232: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.233: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.233: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.233: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.233: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.233: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.233: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.234: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.234: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.234: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.234: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.234: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.234: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.235: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.235: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.235: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.235: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.235: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.235: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.236: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.236: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.236: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.236: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.236: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.236: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.236: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.236: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.237: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.237: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.237: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.237: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.237: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.237: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.238: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.238: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.238: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.238: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.238: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.238: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.239: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.239: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.239: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.239: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.239: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.239: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.240: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.240: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.240: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.240: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.240: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.240: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.241: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.241: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.241: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.241: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.241: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.241: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.241: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.242: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.242: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.242: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.242: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.242: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.243: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.243: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.243: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.243: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.243: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.243: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.244: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.244: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.244: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.244: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.244: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.244: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.245: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.245: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.245: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.245: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.245: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.245: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.246: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.246: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.246: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.246: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.246: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.246: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.246: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.247: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.247: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.247: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.247: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.247: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.247: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.247: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.248: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.248: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.248: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.248: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.248: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.249: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.249: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.249: variance_after = 20 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.249: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.249: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.249: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.249: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.250: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.250: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.250: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.250: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.250: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.250: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.251: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.251: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.251: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.251: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.251: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.251: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.252: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.252: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.252: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.252: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.252: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.252: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.253: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.253: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.253: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.253: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.253: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.253: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.254: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.254: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.254: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.254: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.254: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.254: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.255: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.255: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.255: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.255: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.255: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.255: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.256: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.256: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.256: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.256: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.256: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.256: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.257: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.257: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.257: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.257: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.257: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.257: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.258: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.258: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.258: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.258: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.258: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.258: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.259: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.259: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.259: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.259: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.259: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.259: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.260: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.260: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.260: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.260: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.260: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.260: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.260: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.260: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.261: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.261: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.261: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.261: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.261: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.261: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.262: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.262: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.262: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.262: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.262: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.262: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.263: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.263: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.263: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.263: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.263: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.263: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.264: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.264: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.264: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.264: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.264: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.264: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.265: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.265: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.265: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.265: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.265: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.265: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.266: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.266: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.266: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.266: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.266: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.266: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.267: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.267: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.267: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.267: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.267: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.267: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.268: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.268: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.268: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.268: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.268: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.268: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.268: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.268: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.269: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.269: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.269: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.269: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.269: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.269: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.270: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.270: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.270: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.270: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.270: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.270: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.271: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.271: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.271: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.271: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.271: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.271: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.272: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.272: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.272: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.272: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.272: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.272: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.273: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.273: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.273: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.273: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.273: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.273: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.274: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.274: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.274: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.274: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.274: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.274: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.275: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.275: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.275: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.275: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.275: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.275: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.276: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.276: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.276: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.276: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.276: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.276: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.277: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.277: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.277: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.277: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.277: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.277: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.277: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.277: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.278: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.278: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.278: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.278: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.278: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.278: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.279: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.279: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.279: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.279: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.279: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.279: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.280: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.280: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.280: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.280: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.280: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.280: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.281: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.281: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.281: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.281: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.281: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.281: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.282: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.282: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.282: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.282: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.282: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.282: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.283: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.283: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.283: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.283: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.283: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.283: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.284: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.284: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.284: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.284: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.284: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.284: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.284: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.285: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.285: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.285: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.285: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.285: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.285: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.285: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.286: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.286: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.286: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.286: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.286: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.286: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.287: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.287: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.287: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.287: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.287: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.287: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.288: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.288: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.288: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.288: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.288: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.288: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.289: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.289: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.289: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.289: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.289: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.289: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.290: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.290: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.290: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.290: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.290: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.290: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.291: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.291: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.291: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.291: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.291: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.291: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.292: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.292: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.292: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.292: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.292: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.292: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.292: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.292: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.293: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.293: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.293: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.293: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.293: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.294: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.294: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.294: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.294: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.294: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.294: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.295: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.295: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.295: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.295: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.295: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.295: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.296: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.296: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.296: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.296: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.296: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.296: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.297: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.297: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.297: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.297: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.297: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.297: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.297: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.297: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.298: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.298: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.298: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.298: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.298: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.298: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.299: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.299: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.299: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.299: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.299: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.299: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.300: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.300: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.300: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.300: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.300: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.300: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.301: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.301: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.301: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.301: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.301: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.301: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.302: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.302: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.302: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.302: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.302: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.302: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.303: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.303: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.303: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.303: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.303: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.303: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.304: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.304: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.304: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.304: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.304: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.304: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.305: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.305: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.305: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.305: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.305: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.305: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.306: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.306: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.306: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.306: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.306: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.306: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.307: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.307: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.307: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.307: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.307: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.307: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.308: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.308: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.308: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.308: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.308: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.308: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.309: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.309: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.309: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.309: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.309: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.309: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.310: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.310: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.310: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.310: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.310: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.310: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.311: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.311: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.311: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.311: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.311: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.311: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.312: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.312: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.312: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.312: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.312: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.312: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.313: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.313: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.313: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.313: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.313: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.313: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.313: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.313: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.314: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.314: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.314: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.314: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.314: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.314: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.315: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.315: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.315: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.315: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.315: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.315: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.316: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.316: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.316: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.316: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.316: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.316: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.317: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.317: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.317: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.317: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.317: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.317: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.318: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.318: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.318: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.318: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.319: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.319: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.319: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.319: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.319: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.320: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.320: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.320: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.320: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.320: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.320: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.320: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.321: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.321: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.321: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.321: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.321: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.321: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.322: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.322: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.322: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.322: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.322: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.322: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.323: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.323: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.323: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.323: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.323: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.323: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.324: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.324: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.324: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.324: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.324: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.324: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.325: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.325: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.325: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.325: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.325: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.325: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.325: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.326: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.326: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.326: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.326: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.326: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.326: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.326: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.327: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.327: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.327: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.327: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.327: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.327: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.328: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.328: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.328: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.328: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.328: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.328: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.329: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.329: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.329: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.329: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.329: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.329: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.330: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.330: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.330: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.330: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.330: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.330: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.331: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.331: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.331: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.331: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.331: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.331: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.332: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.332: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.332: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.332: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.332: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.332: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.333: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.333: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.333: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.333: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.333: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.333: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.334: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.334: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.334: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.334: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.334: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.334: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.334: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.334: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.335: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.335: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.335: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.335: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.335: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.335: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.336: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.336: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.336: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.336: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.336: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.336: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.337: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.337: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.337: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.337: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.337: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.337: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.338: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.338: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.338: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.338: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.338: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.338: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.339: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.339: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.339: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.339: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.339: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.339: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.340: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.340: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.340: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.340: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.340: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.340: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.340: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.340: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.341: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.341: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.341: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.341: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.341: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.342: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.342: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.342: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.342: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.342: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.342: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.343: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.343: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.343: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.343: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.343: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.343: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.344: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.344: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.344: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.344: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.344: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.344: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.344: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.344: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.345: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.345: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.345: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.345: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.345: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.345: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.346: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.346: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.346: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.346: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.346: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.346: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.347: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.347: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.347: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.347: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.347: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.347: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.348: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.348: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.348: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.348: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.348: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.348: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.349: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.349: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.349: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.349: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.349: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.349: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.350: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.350: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.350: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.350: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.350: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.350: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.351: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.351: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.351: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.351: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.351: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.351: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.352: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.352: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.352: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.352: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.352: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.352: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.353: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.353: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.353: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.353: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.353: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.353: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.354: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.354: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.354: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.354: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.354: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.354: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.355: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.355: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.355: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.355: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.355: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.355: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.355: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.355: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.356: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.356: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.356: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.356: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.356: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.356: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.357: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.357: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.357: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.357: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.357: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.357: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.358: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.358: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.358: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.358: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.358: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.358: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.359: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.359: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.359: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.359: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.359: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.359: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.360: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.360: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.360: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.360: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.360: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.360: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.361: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.361: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.361: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.361: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.361: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.361: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.361: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.362: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.362: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.362: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.362: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.362: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.363: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.363: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.363: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.363: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.363: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.363: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.364: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.364: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.364: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.364: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.364: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.364: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.365: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.365: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.365: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.365: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.365: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.365: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.365: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.366: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.366: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.366: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.366: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.366: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.367: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.367: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.367: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.367: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.367: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.368: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.368: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.368: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.368: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.368: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.368: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.368: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.369: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.369: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.369: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.369: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.369: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.369: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.370: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.370: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.370: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.370: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.370: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.370: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.371: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.371: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.371: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.371: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.371: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.371: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.372: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.372: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.372: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.372: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.372: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.372: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.373: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.373: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.373: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.373: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.373: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.373: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.373: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.373: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.374: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.374: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.374: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.374: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.374: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.374: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.375: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.375: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.375: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.375: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.375: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.375: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.376: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.376: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.376: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.376: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.376: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.376: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.377: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.377: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.377: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.377: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.377: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.377: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.378: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.378: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.378: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.378: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.378: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.378: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.379: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.379: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.379: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.379: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.379: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.379: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.380: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.380: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.380: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.380: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.380: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.380: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.381: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.381: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.381: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.381: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.381: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.381: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.382: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.382: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.382: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.382: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.382: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.382: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.383: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.383: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.383: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.383: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.383: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.383: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.384: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.384: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.384: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.384: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.384: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.384: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.385: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.385: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.385: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.385: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.385: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.385: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.386: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.386: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.386: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.386: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.386: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.386: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.387: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.387: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.387: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.387: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.387: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.387: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.387: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.387: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.388: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.388: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.388: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.388: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.388: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.388: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.389: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.389: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.389: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.389: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.389: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.389: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.390: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.390: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.390: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.390: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.390: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.390: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.391: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.391: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.391: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.391: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.391: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.391: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.392: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.392: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.392: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.392: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.392: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.392: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.393: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.393: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.393: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.393: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.393: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.393: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.394: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.394: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.394: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.394: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.394: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.394: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.394: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.395: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.395: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.395: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.395: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.395: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.396: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.396: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.396: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.396: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.396: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.396: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.397: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.397: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.397: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.397: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.397: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.397: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.398: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.398: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.398: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.398: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.398: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.398: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.399: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.399: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.399: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.399: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.399: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.399: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.400: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.400: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.400: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.400: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.400: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.400: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.401: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.401: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.401: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.401: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.401: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.401: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.401: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.402: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.402: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.402: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.402: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.402: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.402: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.402: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.403: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.403: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.403: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.403: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.403: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.403: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.404: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.404: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.404: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.404: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.404: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.404: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.405: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.405: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.405: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.405: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.405: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.405: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.406: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.406: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.406: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.406: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.406: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.406: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.407: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.407: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.407: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.407: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.407: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.407: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.408: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.408: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.408: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.408: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.408: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.408: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.409: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.409: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.409: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.409: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.409: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.409: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.410: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.410: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.410: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.410: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.410: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.410: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.411: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.411: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.411: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.411: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.411: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.411: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.411: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.412: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.412: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.412: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.412: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.412: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.413: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.413: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.413: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.413: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.413: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.414: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.414: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.414: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.414: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.414: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.414: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.414: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.415: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.415: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.415: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.415: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.415: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.415: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.416: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.416: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.416: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.416: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.416: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.416: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.417: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.417: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.417: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.417: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.417: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.417: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.418: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.418: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.418: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.418: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.418: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.418: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.419: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.419: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.419: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.419: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.419: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.419: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.420: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.420: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.420: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.420: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.420: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.420: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.421: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.421: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.421: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.421: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.421: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.421: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.422: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.422: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.422: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.422: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.422: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.422: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.422: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.423: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.423: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.423: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.423: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.423: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.423: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.423: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.424: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.424: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.424: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.424: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.424: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.424: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.425: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.425: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.425: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.425: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.425: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.425: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.426: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.426: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.426: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.426: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.426: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.426: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.426: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.426: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.427: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.427: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.427: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.427: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.427: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.427: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.427: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.427: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.428: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.428: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.428: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.428: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.428: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.428: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.429: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.429: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.429: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.429: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.429: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.429: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.430: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.430: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.430: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.430: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.430: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.430: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.431: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.431: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.431: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.431: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.431: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.431: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.432: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.432: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.432: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.432: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.432: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.432: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.432: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.433: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.433: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.433: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.433: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.433: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.433: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.433: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.434: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.434: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.434: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.434: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.434: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.434: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.435: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.435: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.435: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.435: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.435: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.435: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.436: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.436: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.436: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.436: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.436: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.436: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.437: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.437: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.437: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.437: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.437: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.437: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.438: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.438: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.438: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.438: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.438: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.439: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.439: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.439: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.439: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.439: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.439: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.439: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.440: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.440: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.440: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.440: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.440: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.440: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.441: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.441: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.441: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.441: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.441: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.441: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.442: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.442: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.442: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.442: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.442: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.442: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.443: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.443: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.443: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.443: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.443: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.443: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.444: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.444: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.444: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.444: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.444: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.444: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.444: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.444: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.445: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.445: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.445: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.445: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.445: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.445: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.446: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.446: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.446: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.446: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.446: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.446: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.447: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.447: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.447: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.447: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.447: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.447: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.448: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.448: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.448: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.448: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.448: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.448: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.449: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.449: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.449: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.449: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.449: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.449: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.450: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.450: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.450: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.450: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.450: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.450: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.451: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.451: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.451: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.451: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.451: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.451: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.452: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.452: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.452: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.452: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.452: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.452: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.452: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.452: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.452: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.453: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.453: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.453: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.453: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.453: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.454: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.454: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.454: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.454: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.454: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.455: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.455: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.455: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.455: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.455: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.455: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.455: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.456: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.456: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.456: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.456: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.456: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.456: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.457: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.457: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.457: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.457: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.457: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.457: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.458: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.458: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.458: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.458: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.458: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.458: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.459: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.459: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.459: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.459: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.459: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.459: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.460: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.460: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.460: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.460: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.460: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.460: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.461: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.461: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.461: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.461: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.461: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.461: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.462: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.462: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.462: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.462: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.462: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.462: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.463: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.463: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.463: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.463: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.463: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.463: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.463: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.464: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.464: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.464: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.464: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.464: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.464: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.464: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.465: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.465: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.465: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.465: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.465: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.465: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.466: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.466: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.466: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.466: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.466: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.466: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.467: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.467: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.467: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.467: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.467: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.467: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.468: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.468: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.468: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.468: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.468: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.468: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.469: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.469: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.469: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.469: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.469: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.469: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.470: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.470: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.470: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.470: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.470: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.470: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.471: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.471: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.471: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.471: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.471: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.471: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.472: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.472: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.472: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.472: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.472: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.472: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.473: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.473: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.473: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.473: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.473: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.473: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.474: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.474: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.474: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.474: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.474: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.474: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.474: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.474: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.475: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.475: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.475: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.475: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.475: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.475: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.476: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.476: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.476: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.476: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.476: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.476: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.477: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.477: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.477: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.477: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.477: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.477: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.478: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.478: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.478: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.478: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.478: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.478: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.479: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.479: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.479: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.479: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.479: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.479: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.480: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.480: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.480: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.480: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.480: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.480: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.481: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.481: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.481: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.481: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.481: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.481: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.482: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.482: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.482: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.482: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.482: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.482: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.483: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.483: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.483: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.483: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.483: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.483: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.484: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.484: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.484: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.484: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.484: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.484: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.484: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.484: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.485: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.485: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.485: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.485: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.485: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.485: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.486: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.486: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.486: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.486: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.486: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.486: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.487: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.487: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.487: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.487: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.487: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.487: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.488: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.488: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.488: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.488: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.488: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.488: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.489: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.489: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.489: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.489: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.489: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.489: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.490: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.490: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.490: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.490: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.491: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.491: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.491: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.491: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.491: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.491: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.491: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.491: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.492: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.492: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.492: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.492: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.492: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.492: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.493: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.493: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.493: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.493: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.493: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.493: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.494: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.494: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.494: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.494: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.494: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.494: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.495: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.495: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.495: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.495: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.495: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.495: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.496: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.496: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.496: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.496: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.496: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.496: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.496: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.496: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.496: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.497: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.497: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.497: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.497: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.497: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.498: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.498: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.498: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.498: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.498: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.499: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.499: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.499: variance_after = 16 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.499: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.499: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.499: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.499: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.500: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.500: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.500: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.500: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.500: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.500: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.501: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.501: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.501: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.501: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.501: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.501: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.502: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.502: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.502: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.502: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.502: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.502: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.503: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.503: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.503: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.503: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.503: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.503: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.504: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.504: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.504: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.504: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.504: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.504: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.505: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.505: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.505: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.505: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.505: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.505: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.506: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.506: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.506: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.506: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.506: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.506: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.507: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.507: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.507: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.507: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.507: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.507: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.508: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.508: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.508: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.508: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.508: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.508: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.509: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.509: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.509: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.509: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.509: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.509: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.509: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.509: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.510: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.510: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.510: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.510: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.510: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.510: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.511: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.511: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.511: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.511: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.511: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.511: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.512: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.512: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.512: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.512: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.512: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.512: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.513: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.513: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.513: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.513: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.513: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.513: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.514: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.514: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.514: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.514: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.514: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.514: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.515: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.515: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.515: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.515: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.515: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.515: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.516: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.516: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.516: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.516: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.516: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.516: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.516: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.517: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.517: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.517: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.517: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.517: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.518: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.518: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.518: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.518: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.518: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.518: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.519: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.519: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.519: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.519: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.519: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.519: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.520: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.520: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.520: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.520: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.520: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.520: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.521: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.521: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.521: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.521: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.521: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.521: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.521: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.521: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.522: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.522: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.522: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.522: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.522: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.522: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.523: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.523: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.523: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.523: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.523: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.523: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.524: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.524: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.524: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.524: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.524: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.524: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.525: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.525: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.525: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.525: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.525: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.525: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.525: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.526: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.526: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.526: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.526: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.526: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.527: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.527: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.527: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.527: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.527: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.527: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.528: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.528: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.528: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.528: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.528: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.528: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.529: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.529: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.529: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.529: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.529: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.529: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.529: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.529: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.530: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.530: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.530: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.530: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.530: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.530: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.531: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.531: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.531: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.531: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.531: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.531: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.532: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.532: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.532: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.532: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.532: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.532: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.533: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.533: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.533: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.533: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.533: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.533: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.534: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.534: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.534: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.534: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.534: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.534: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.535: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.535: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.535: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.535: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.535: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.535: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.536: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.536: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.536: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.536: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.536: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.536: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.537: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.537: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.537: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.537: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.537: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.537: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.538: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.538: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.538: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.538: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.538: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.538: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.538: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.538: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.539: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.539: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.539: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.539: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.539: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.539: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.539: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.540: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.540: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.540: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.540: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.540: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.540: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.540: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.541: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.541: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.541: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.541: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.541: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.542: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.542: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.542: variance_after = 17 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.542: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.542: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.542: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.542: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.543: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.543: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.543: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.543: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.543: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.544: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.544: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.544: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.544: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.544: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.544: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.544: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.545: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.545: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.545: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.545: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.545: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.545: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.546: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.546: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.546: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.546: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.546: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.546: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.547: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.547: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.547: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.547: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.547: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.547: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.548: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.548: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.548: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.548: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.548: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.548: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.549: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.549: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.549: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.549: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.549: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.549: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.550: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.550: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.550: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.550: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.550: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.550: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.551: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.551: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.551: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.551: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.551: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.551: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.552: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.552: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.552: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.552: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.552: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.552: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.552: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.553: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.553: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.553: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.553: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.553: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.554: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.554: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.554: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.554: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.554: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.554: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.555: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.555: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.555: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.555: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.555: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.555: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.556: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.556: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.556: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.556: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.556: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.556: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.557: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.557: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.557: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.557: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.557: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.557: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.558: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.558: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.558: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.558: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.558: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.558: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.558: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.558: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.559: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.559: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.559: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.559: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.559: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.559: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.560: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.560: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.560: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.560: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.560: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.560: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.561: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.561: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.561: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.561: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.561: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.561: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.562: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.562: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.562: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.562: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.562: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.562: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.563: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.563: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.563: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.563: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.563: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.563: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.564: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.564: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.564: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.564: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.564: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.564: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.565: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.565: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.565: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.565: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.565: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.565: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.566: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.566: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.566: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.566: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.566: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.566: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.567: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.567: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.567: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.567: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.567: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.567: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.568: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.568: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.568: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.568: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.568: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.568: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.569: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.569: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.569: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.569: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.569: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.569: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.570: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.570: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.570: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.570: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.570: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.570: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.571: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.571: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.571: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.571: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.571: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.571: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.572: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.572: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.572: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.572: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.572: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.572: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.573: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.573: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.573: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.573: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.573: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.573: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.573: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.573: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.574: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.574: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.574: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.574: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.574: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.574: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.575: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.575: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.575: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.575: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.575: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.575: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.576: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.576: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.576: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.576: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.576: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.576: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.577: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.577: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.577: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.577: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.577: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.577: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.578: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.578: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.578: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.578: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.578: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.578: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.579: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.579: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.579: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.579: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.579: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.579: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.580: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.580: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.580: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.580: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.580: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.580: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.580: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.581: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.581: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.581: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.581: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.581: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.582: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.582: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.582: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.582: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.582: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.582: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.583: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.583: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.583: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.583: variance_after = 16 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.583: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.583: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.584: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.584: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.584: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.584: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.584: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.584: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.585: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.585: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.585: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.585: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.585: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.585: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.586: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.586: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.586: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.586: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.586: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.586: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.586: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.586: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.587: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.587: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.587: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.587: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.587: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.587: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.588: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.588: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.588: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.588: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.588: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.588: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.589: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.589: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.589: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.589: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.589: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.589: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.590: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.590: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.590: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.590: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.590: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.590: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.591: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.591: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.591: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.591: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.591: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.591: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.592: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.592: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.592: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.592: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.592: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.592: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.593: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.593: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.593: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.593: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.593: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.593: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.594: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.594: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.594: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.594: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.594: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.594: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.594: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.595: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.595: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.595: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.595: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.595: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.595: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.595: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.596: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.596: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.596: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.596: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.596: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.596: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.597: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.597: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.597: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.597: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.597: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.597: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.598: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.598: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.598: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.598: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.598: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.598: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.599: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.599: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.599: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.599: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.599: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.599: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.600: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.600: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.600: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.600: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.600: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.600: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.601: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.601: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.601: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.601: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.601: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.601: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.602: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.602: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.602: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.602: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.602: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.602: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.603: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.603: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.603: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.603: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.603: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.603: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.604: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.604: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.604: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.604: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.604: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.604: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.604: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.604: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.604: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.604: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.605: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.605: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.605: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.605: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.605: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.605: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.606: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.606: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.606: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.606: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.606: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.606: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.607: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.607: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.607: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.607: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.607: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.607: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.608: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.608: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.608: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.608: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.608: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.608: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.609: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.609: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.609: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.609: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.609: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.609: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.609: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.610: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.610: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.610: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.610: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.610: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.611: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.611: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.611: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.611: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.611: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.611: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.612: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.612: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.612: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.612: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.612: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.612: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.613: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.613: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.613: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.613: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.613: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.613: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.614: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.614: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.614: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.614: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.614: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.614: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.615: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.615: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.615: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.615: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.615: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.615: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.615: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.615: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.616: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.616: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.616: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.616: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.616: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.616: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.617: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.617: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.617: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.617: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.617: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.617: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.618: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.618: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.618: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.618: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.618: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.618: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.619: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.619: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.619: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.619: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.619: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.619: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.620: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.620: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.620: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.620: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.620: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.620: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.620: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.621: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.621: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.621: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.621: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.621: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.622: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.622: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.622: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.622: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.622: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.622: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.623: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.623: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.623: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.623: variance_after = 2168 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.623: [vfs7552] CAPTURE_NUM_STATES completed successfully 191s (process:4246): libfprint-device-DEBUG: 20:26:39.623: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 191s (process:4246): libfprint-image_device-DEBUG: 20:26:39.623: Image device reported finger status: on 191s (process:4246): libfprint-image_device-DEBUG: 20:26:39.623: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.673: changing to 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.673: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.673: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.674: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.674: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.674: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.674: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.674: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.674: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.674: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.675: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.675: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.675: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.675: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.675: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.676: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.676: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.676: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.676: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.676: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.676: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.677: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.677: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.677: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.677: variance_after = 2082 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.677: [vfs7552] CAPTURE_NUM_STATES completed successfully 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.677: Image captured 191s (process:4246): libfprint-image_device-DEBUG: 20:26:39.677: Image device captured an image 191s (process:4246): libfprint-image_device-DEBUG: 20:26:39.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 191s (process:4246): libfprint-device-DEBUG: 20:26:39.677: Device reported finger status change: FP_FINGER_STATUS_PRESENT 191s (process:4246): libfprint-image-DEBUG: 20:26:39.689: Minutiae scan completed in 0.011462 secs 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.727: changing to 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.727: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.727: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.728: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.728: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.729: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.729: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.729: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.729: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.729: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.729: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.729: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.730: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.730: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.730: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.731: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.731: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.731: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.731: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.731: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.732: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.732: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.733: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.733: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.733: variance_after = 2003 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.733: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.733: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.733: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.733: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.734: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.734: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.734: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.734: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.734: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.734: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.735: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.735: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.735: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.735: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.736: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.736: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.736: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.736: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.736: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.736: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.737: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.737: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.738: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.738: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.738: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.738: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.738: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.738: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.739: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.739: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.739: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.739: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.739: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.739: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.740: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.740: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.740: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.740: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.740: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.740: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.741: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.741: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.741: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.741: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.741: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.741: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.742: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.742: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.742: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.742: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.743: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.743: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.743: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.743: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.743: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.743: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.744: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.744: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.744: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.744: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.744: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.744: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.745: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.745: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.746: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.746: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.746: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.746: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.746: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.746: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.747: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.747: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.747: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.747: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.747: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.747: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.748: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.748: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.748: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.748: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.749: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.749: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.749: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.749: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.749: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.749: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.750: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.750: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.751: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.751: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.751: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.751: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.751: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.751: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.752: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.752: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.752: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.752: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.752: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.752: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.753: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.753: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.753: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.753: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.753: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.753: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.753: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.754: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.754: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.754: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.754: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.754: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.755: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.755: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.755: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.755: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.755: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.755: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.756: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.756: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.756: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.756: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.756: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.756: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.757: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.757: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.757: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.757: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.757: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.757: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.758: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.758: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.758: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.758: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.758: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.758: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.759: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.759: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.759: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.759: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.759: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.760: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.760: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.760: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.760: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.760: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.760: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.761: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.761: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.761: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.761: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.761: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.761: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.762: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.762: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.762: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.762: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.762: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.762: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.763: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.763: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.763: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.763: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.763: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.763: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.764: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.764: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.764: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.764: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.764: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.764: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.765: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.765: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.765: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.765: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.765: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.765: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.766: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.766: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.766: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.766: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.766: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.766: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.767: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.767: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.767: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.767: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.767: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.767: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.768: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.768: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.768: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.768: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.768: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.768: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.769: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.769: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.769: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.769: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.769: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.770: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.770: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.770: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.771: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.771: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.771: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.771: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.771: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.771: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.772: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.772: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.772: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.772: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.772: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.772: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.773: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.773: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.773: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.773: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.773: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.773: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.774: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.774: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.774: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.774: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.774: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.774: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.775: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.775: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.775: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.775: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.775: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.775: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.776: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.776: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.776: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.776: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.777: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.777: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.777: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.777: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.777: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.777: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.778: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.778: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.778: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.778: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.778: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.778: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.779: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.779: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.779: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.779: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.779: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.779: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.780: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.780: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.780: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.780: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.780: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.780: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.781: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.781: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.781: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.781: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.781: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.781: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.782: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.782: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.782: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.783: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.783: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.783: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.783: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.784: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.784: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.784: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.784: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.784: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.784: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.784: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.785: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.785: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.786: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.786: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.786: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.786: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.786: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.786: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.787: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.787: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.787: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.787: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.787: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.787: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.788: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.788: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.788: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.788: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.788: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.788: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.789: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.789: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.789: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.789: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.789: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.790: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.790: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.790: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.790: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.790: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.791: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.791: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.791: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.791: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.791: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.791: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.792: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.792: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.792: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.792: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.792: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.792: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.793: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.793: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.793: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.793: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.793: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.793: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.794: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.794: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.794: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.794: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.794: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.794: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.795: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.795: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.795: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.795: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.795: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.795: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.796: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.796: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.796: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.796: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.796: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.796: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.797: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.797: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.797: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.797: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.797: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.797: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.798: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.798: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.798: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.798: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.798: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.798: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.799: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.799: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.799: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.799: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.799: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.799: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.800: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.800: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.800: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.800: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.800: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.800: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.801: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.801: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.801: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.801: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.801: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.801: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.802: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.802: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.802: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.802: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.802: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.802: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.803: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.803: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.803: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.803: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.803: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.803: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.804: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.804: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.804: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.804: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.804: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.804: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.805: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.805: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.805: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.805: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.805: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.805: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.806: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.806: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.806: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.806: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.806: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.806: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.807: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.807: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.807: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.807: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.807: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.807: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.807: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.808: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.808: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.808: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.808: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.808: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.808: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.809: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.809: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.809: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.809: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.809: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.809: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.810: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.810: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.810: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.810: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.810: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.810: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.811: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.811: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.811: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.811: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.811: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.811: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.812: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.812: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.812: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.812: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.812: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.812: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.813: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.813: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.813: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.813: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.813: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.813: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.814: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.814: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.814: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.814: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.814: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.814: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.815: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.815: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.815: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.815: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.815: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.815: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.816: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.816: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.816: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.816: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.817: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.817: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.817: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.817: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.817: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.818: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.818: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.818: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.818: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.818: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.819: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.819: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.819: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.820: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.820: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.820: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.820: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.820: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.821: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.821: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.821: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.821: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.821: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.821: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.822: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.822: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.822: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.822: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.822: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.822: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.823: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.823: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.823: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.823: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.823: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.823: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.824: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.824: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.824: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.824: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.825: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.825: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.825: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.825: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.825: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.825: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.825: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.825: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.826: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.826: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.826: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.826: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.826: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.826: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.827: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.827: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.827: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.827: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.827: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.827: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.828: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.828: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.828: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.828: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.828: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.828: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.829: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.829: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.829: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.829: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.829: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.829: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.830: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.830: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.830: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.830: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.830: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.830: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.831: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.831: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.831: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.831: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.831: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.831: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.832: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.832: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.833: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.833: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.833: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.833: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.833: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.833: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.834: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.834: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.834: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.834: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.835: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.835: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.835: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.835: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.836: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.836: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.836: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.836: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.836: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.836: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.837: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.837: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.837: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.837: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.837: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.837: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.838: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.838: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.838: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.838: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.838: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.838: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.839: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.839: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.839: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.839: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.839: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.839: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.840: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.840: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.840: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.840: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.840: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.841: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.841: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.841: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.841: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.841: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.842: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.842: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.842: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.842: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.842: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.842: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.843: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.843: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.843: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.843: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.843: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.843: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.844: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.844: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.844: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.844: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.844: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.844: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.845: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.845: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.845: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.845: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.845: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.845: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.846: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.846: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.846: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.847: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.847: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.847: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.847: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.847: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.847: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.848: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.848: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.848: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.848: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.848: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.848: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.848: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.849: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.849: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.849: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.849: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.849: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.850: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.850: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.850: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.851: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.851: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.851: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.851: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.851: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.851: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.852: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.852: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.852: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.852: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.852: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.852: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.853: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.853: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.853: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.853: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.853: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.853: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.854: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.854: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.854: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.854: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.854: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.854: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.855: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.855: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.855: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.855: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.855: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.855: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.856: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.856: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.856: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.856: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.856: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.856: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.857: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.857: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.857: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.857: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.857: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.857: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.858: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.858: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.858: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.858: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.858: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.858: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.859: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.859: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.859: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.859: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.859: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.859: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.860: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.860: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.860: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.860: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.860: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.860: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.861: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.861: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.861: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.861: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.861: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.861: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.862: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.862: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.862: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.862: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.862: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.862: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.863: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.863: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.864: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.864: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.864: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.864: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.864: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.864: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.865: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.865: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.865: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.865: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.865: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.865: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.866: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.866: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.866: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.866: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.866: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.866: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.867: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.867: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.867: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.867: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.867: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.867: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.868: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.868: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.868: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.868: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.869: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.869: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.869: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.869: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.869: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.869: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.870: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.870: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.870: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.870: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.870: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.870: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.871: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.871: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.871: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.871: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.871: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.871: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.872: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.872: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.873: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.873: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.873: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.873: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.873: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.873: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.874: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.874: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.874: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.874: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.874: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.874: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.875: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.875: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.875: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.875: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.875: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.875: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.876: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.876: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.876: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.876: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.876: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.876: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.877: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.877: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.877: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.877: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.877: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.877: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.878: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.878: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.878: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.878: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.878: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.878: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.879: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.879: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.879: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.879: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.879: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.879: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.880: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.880: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.880: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.880: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.880: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.880: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.881: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.881: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.881: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.881: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.881: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.881: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.882: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.882: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.882: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.882: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.882: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.882: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.883: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.883: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.883: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.883: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.883: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.883: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.884: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.884: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.885: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.885: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.885: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.885: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.885: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.885: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.886: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.886: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.886: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.886: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.886: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.886: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.887: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.887: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.887: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.887: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.887: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.887: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.888: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.888: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.888: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.888: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.888: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.888: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.889: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.889: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.889: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.889: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.890: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.890: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.890: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.890: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.890: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.890: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.891: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.891: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.891: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.891: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.891: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.891: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.892: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.892: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.892: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.892: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.892: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.892: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.893: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.893: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.893: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.893: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.893: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.893: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.894: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.894: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.894: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.894: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.894: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.894: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.895: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.895: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.895: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.895: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.895: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.895: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.895: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.896: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.896: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.896: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.896: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.896: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.896: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.896: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.897: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.897: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.897: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.897: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.898: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.898: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.898: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.898: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.898: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.898: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.899: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.899: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.899: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.899: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.899: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.899: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.899: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.900: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.900: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.900: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.900: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.900: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.901: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.901: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.901: [vfs7552] CAPTURE_NUM_STATES entering state 2 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.901: [vfs7552] REQUEST CHUNK entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.901: Sending vfs7552_read_image_chunk 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.901: [vfs7552] REQUEST CHUNK completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.902: [vfs7552] CAPTURE_NUM_STATES entering state 3 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.902: [vfs7552] CAPTURE_NUM_STATES entering state 4 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.902: Cleaning image 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.902: variance_after = 1737 191s 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.902: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.902: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.902: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.902: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.903: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.903: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.903: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.903: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.903: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.903: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.904: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.904: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.904: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.904: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.904: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.905: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.905: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.905: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.905: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.905: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.906: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.906: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.906: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.906: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.906: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.906: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.907: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.907: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.907: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.907: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.907: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.907: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.907: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.908: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.908: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.908: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.908: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.908: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.908: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.908: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.909: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.909: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.909: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.909: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.910: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.910: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.910: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.910: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.910: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.910: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.910: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.910: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.911: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.911: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.911: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.911: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.911: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.912: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.912: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.912: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.913: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.913: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.913: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.913: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.913: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.913: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.914: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.914: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.914: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.914: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.914: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.914: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.915: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.915: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.915: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.915: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.915: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.915: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.916: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.916: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.916: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.916: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.916: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.916: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.917: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.917: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.917: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.917: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.917: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.917: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.917: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.918: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.918: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.918: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.918: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.918: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.919: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.919: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.919: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.919: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.919: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.920: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.920: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.920: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.920: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.920: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.920: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.920: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.920: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.921: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.921: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.921: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.921: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.921: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.921: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.922: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.922: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.922: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.922: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.922: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.922: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.923: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.923: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.923: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.923: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.923: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.923: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.924: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.924: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.924: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.924: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.924: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.924: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.925: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.925: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.925: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.925: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.925: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.925: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.926: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.926: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.926: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.926: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.926: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.926: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.927: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.927: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.927: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.927: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.927: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.927: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.928: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.928: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.928: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.928: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.928: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.928: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.929: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.929: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.929: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.929: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.929: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.929: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.930: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.930: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.930: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.930: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.930: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.930: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.931: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.931: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.931: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.931: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.931: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.931: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.932: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.932: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.932: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.932: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.932: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.932: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.933: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.933: Receiving 64 bytes 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.933: Got 6 bytes out of 64 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.933: [vfs7552] QUERY DATA READY completed successfully 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.933: [vfs7552] QUERY DATA READY entering state 0 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.933: Sending vfs7552_is_image_ready 191s (process:4246): libfprint-SSM-DEBUG: 20:26:39.934: [vfs7552] QUERY DATA READY entering state 1 191s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.934: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.934: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.934: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.934: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.934: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.935: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.935: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.935: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.935: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.935: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.935: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.936: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.936: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.936: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.936: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.936: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.936: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.937: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.937: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.937: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.937: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.937: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.937: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.938: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.938: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.938: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.938: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.938: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.938: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.939: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.939: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.939: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.939: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.939: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.939: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.940: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.940: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.940: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.940: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.940: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.940: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.941: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.941: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.941: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.941: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.941: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.941: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.942: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.942: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.943: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.943: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.943: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.943: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.943: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.943: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.944: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.944: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.944: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.944: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.945: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.945: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.945: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.945: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.945: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.946: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.946: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.946: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.946: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.946: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.947: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.947: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.947: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.947: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.947: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.947: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.948: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.948: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.948: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.948: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.948: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.948: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.948: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.949: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.949: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.949: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.949: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.949: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.950: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.950: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.950: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.950: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.950: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.950: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.951: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.951: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.951: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.951: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.951: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.951: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.952: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.952: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.952: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.952: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.952: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.952: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.953: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.953: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.953: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.953: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.953: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.953: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.954: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.954: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.954: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.954: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.954: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.954: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.955: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.955: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.955: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.955: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.955: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.955: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.956: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.956: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.956: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.956: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.956: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.956: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.957: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.957: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.957: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.957: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.957: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.957: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.958: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.958: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.958: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.958: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.958: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.958: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.959: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.959: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.959: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.959: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.959: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.959: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.960: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.960: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.960: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.960: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.960: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.960: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.961: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.961: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.961: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.961: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.961: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.961: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.962: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.962: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.962: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.962: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.962: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.962: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.962: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.963: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.963: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.963: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.963: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.963: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.963: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.964: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.964: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.964: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.964: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.964: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.964: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.964: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.965: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.965: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.965: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.965: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.965: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.965: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.966: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.966: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.966: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.966: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.966: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.966: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.967: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.967: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.967: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.967: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.967: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.967: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.968: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.968: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.968: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.968: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.968: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.968: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.969: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.969: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.969: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.969: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.969: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.969: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.970: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.970: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.970: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.970: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.970: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.970: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.971: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.971: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.972: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.972: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.972: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.972: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.972: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.972: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.973: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.973: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.973: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.973: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.973: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.973: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.974: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.974: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.974: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.974: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.974: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.974: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.975: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.975: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.975: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.975: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.975: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.975: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.976: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.976: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.976: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.976: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.976: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.976: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.977: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.977: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.977: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.977: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.977: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.977: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.977: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.978: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.978: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.978: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.978: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.978: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.979: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.979: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.979: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.979: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.979: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.979: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.980: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.980: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.980: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.980: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.980: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.980: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.981: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.981: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.981: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.981: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.981: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.981: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.982: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.982: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.982: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.982: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.982: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.982: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.983: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.983: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.983: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.983: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.983: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.983: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.983: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.984: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.984: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.984: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.984: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.984: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.984: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.984: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.985: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.985: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.985: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.985: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.985: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.985: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.986: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.986: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.986: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.986: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.986: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.986: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.987: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.987: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.987: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.987: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.987: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.987: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.988: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.988: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.988: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.988: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.988: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.988: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.989: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.989: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.989: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.989: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.989: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.989: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.990: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.990: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.990: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.990: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.990: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.990: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.991: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.991: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.991: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.991: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.991: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.991: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.992: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.992: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.992: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.992: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.992: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.992: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.993: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.993: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.993: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.993: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.993: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.993: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.993: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.993: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.994: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.994: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.994: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.994: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.994: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.994: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.995: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.995: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.995: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.995: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.995: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.995: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.996: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.996: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.996: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.996: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.996: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.996: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.997: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.997: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.997: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.997: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.997: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.997: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.997: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.998: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.998: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.998: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.998: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.998: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.999: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.999: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.999: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.999: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:39.999: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:39.999: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.000: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.000: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.000: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.000: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.000: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.000: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.000: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.001: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.001: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.001: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.001: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.001: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.001: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.001: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.002: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.002: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.002: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.002: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.002: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.002: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.003: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.003: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.003: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.003: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.003: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.003: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.003: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.003: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.004: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.004: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.004: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.004: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.004: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.005: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.005: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.005: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.005: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.005: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.005: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.006: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.006: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.006: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.006: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.006: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.006: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.007: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.007: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.007: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.007: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.007: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.007: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.008: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.008: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.008: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.008: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.008: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.008: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.009: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.009: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.009: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.009: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.009: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.009: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.010: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.010: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.010: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.010: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.010: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.010: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.011: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.011: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.011: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.011: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.011: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.011: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.011: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.011: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.012: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.012: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.012: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.012: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.012: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.012: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.013: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.013: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.013: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.013: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.013: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.013: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.014: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.014: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.014: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.014: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.014: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.014: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.015: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.015: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.015: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.015: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.015: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.015: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.016: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.016: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.016: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.016: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.016: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.016: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.017: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.017: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.017: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.017: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.017: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.017: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.018: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.018: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.018: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.018: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.018: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.018: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.018: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.019: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.019: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.019: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.019: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.019: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.020: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.020: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.020: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.020: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.020: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.020: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.021: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.021: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.021: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.021: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.021: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.021: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.022: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.022: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.022: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.022: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.022: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.022: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.023: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.023: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.023: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.023: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.023: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.023: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.024: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.024: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.024: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.024: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.024: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.024: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.024: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.024: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.025: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.025: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.025: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.025: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.025: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.025: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.026: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.026: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.026: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.026: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.026: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.026: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.027: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.027: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.027: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.027: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.027: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.027: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.028: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.028: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.028: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.028: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.028: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.028: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.029: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.029: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.029: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.029: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.029: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.029: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.030: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.030: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.030: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.030: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.030: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.030: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.031: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.031: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.031: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.031: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.031: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.031: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.032: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.032: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.032: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.032: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.032: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.032: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.033: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.033: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.033: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.033: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.033: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.033: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.034: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.034: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.034: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.034: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.034: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.034: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.035: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.035: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.035: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.035: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.035: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.035: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.035: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.035: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.036: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.036: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.036: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.036: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.036: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.036: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.037: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.037: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.037: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.037: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.037: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.037: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.038: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.038: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.038: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.038: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.038: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.038: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.038: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.039: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.039: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.039: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.039: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.039: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.040: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.040: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.040: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.040: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.040: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.041: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.041: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.041: variance_after = 1526 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.041: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.041: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.041: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.041: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.042: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.042: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.042: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.042: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.042: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.042: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.043: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.043: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.043: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.043: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.043: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.043: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.044: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.044: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.044: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.044: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.044: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.044: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.045: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.045: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.045: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.045: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.045: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.045: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.045: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.046: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.046: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.046: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.046: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.046: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.047: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.047: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.047: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.047: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.047: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.047: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.048: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.048: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.048: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.048: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.048: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.048: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.049: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.049: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.049: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.049: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.049: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.049: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.050: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.050: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.050: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.050: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.050: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.050: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.051: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.051: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.051: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.051: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.051: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.051: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.051: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.051: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.051: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.052: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.052: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.052: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.052: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.052: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.052: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.052: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.053: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.053: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.053: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.053: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.053: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.053: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.054: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.054: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.054: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.054: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.054: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.054: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.055: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.055: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.055: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.055: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.055: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.055: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.056: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.056: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.056: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.056: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.056: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.056: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.056: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.057: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.057: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.057: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.057: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.057: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.058: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.058: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.058: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.058: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.058: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.058: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.059: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.059: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.059: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.059: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.059: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.059: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.060: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.060: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.060: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.060: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.060: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.060: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.061: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.061: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.061: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.061: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.061: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.061: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.062: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.062: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.062: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.062: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.062: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.062: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.062: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.062: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.063: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.063: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.063: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.063: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.063: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.063: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.064: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.064: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.064: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.064: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.064: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.064: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.065: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.065: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.065: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.065: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.065: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.065: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.065: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.066: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.066: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.066: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.066: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.066: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.067: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.067: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.067: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.067: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.067: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.067: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.068: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.068: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.068: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.068: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.068: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.068: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.069: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.069: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.069: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.069: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.069: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.069: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.070: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.070: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.070: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.070: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.070: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.070: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.070: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.071: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.071: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.071: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.071: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.071: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.071: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.071: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.072: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.072: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.072: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.072: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.072: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.072: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.073: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.073: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.073: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.073: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.073: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.073: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.074: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.074: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.074: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.074: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.074: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.074: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.075: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.075: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.075: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.075: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.075: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.075: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.076: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.076: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.076: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.076: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.076: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.076: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.077: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.077: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.077: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.077: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.077: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.077: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.078: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.078: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.078: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.078: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.078: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.078: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.079: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.079: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.079: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.079: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.079: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.079: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.079: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.079: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.080: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.080: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.080: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.080: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.080: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.080: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.081: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.081: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.081: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.081: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.081: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.081: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.082: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.082: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.082: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.082: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.082: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.082: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.083: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.083: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.083: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.083: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.083: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.083: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.084: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.084: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.084: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.084: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.084: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.084: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.085: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.085: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.085: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.085: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.085: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.085: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.086: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.086: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.086: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.086: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.086: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.086: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.087: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.087: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.087: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.087: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.087: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.087: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.088: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.088: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.088: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.088: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.088: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.088: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.089: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.089: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.089: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.089: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.089: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.089: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.090: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.090: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.090: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.090: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.090: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.090: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.090: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.090: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.091: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.091: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.091: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.091: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.091: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.091: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.092: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.092: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.092: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.092: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.092: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.092: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.093: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.093: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.093: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.093: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.093: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.093: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.094: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.094: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.094: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.094: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.094: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.094: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.094: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.094: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.095: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.095: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.095: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.095: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.095: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.096: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.096: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.096: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.096: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.096: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.096: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.097: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.097: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.097: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.097: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.097: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.097: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.098: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.098: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.098: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.098: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.098: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.098: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.098: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.098: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.099: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.099: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.099: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.099: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.099: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.099: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.100: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.100: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.100: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.100: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.100: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.100: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.101: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.101: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.101: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.101: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.101: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.101: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.102: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.102: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.102: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.102: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.102: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.102: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.103: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.103: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.103: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.103: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.103: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.103: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.104: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.104: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.104: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.104: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.104: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.104: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.105: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.105: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.105: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.105: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.105: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.105: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.106: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.106: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.106: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.106: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.106: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.106: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.107: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.107: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.107: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.107: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.107: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.107: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.108: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.108: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.108: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.108: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.108: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.108: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.109: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.109: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.109: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.109: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.109: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.109: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.109: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.110: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.110: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.110: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.110: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.110: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.110: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.110: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.111: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.111: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.111: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.111: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.111: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.111: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.112: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.112: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.112: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.112: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.112: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.112: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.113: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.113: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.113: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.113: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.113: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.113: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.114: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.114: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.114: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.114: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.114: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.114: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.115: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.115: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.115: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.115: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.115: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.115: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.116: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.116: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.116: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.116: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.116: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.116: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.117: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.117: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.117: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.117: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.117: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.117: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.118: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.118: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.118: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.118: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.118: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.118: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.119: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.119: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.119: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.119: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.119: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.119: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.120: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.120: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.120: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.120: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.120: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.120: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.120: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.120: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.121: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.121: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.121: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.121: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.121: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.121: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.122: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.122: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.122: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.122: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.122: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.123: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.123: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.123: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.123: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.123: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.123: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.123: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.124: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.124: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.124: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.124: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.124: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.124: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.125: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.125: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.125: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.125: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.125: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.125: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.126: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.126: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.126: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.126: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.126: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.126: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.127: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.127: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.127: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.127: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.127: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.127: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.128: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.128: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.128: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.128: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.128: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.128: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.129: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.129: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.129: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.129: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.129: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.129: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.130: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.130: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.130: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.130: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.130: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.130: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.131: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.131: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.131: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.131: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.131: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.131: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.132: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.132: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.132: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.132: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.132: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.132: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.133: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.133: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.133: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.133: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.133: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.133: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.134: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.134: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.134: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.134: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.134: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.134: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.135: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.135: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.135: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.135: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.135: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.135: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.135: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.135: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.136: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.136: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.136: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.136: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.136: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.137: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.137: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.137: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.137: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.137: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.137: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.137: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.138: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.138: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.138: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.138: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.138: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.138: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.139: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.139: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.139: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.139: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.139: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.139: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.140: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.140: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.140: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.140: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.140: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.140: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.141: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.141: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.141: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.141: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.141: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.141: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.142: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.142: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.142: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.142: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.142: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.142: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.143: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.143: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.143: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.143: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.143: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.143: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.144: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.144: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.144: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.144: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.144: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.144: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.145: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.145: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.145: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.145: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.145: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.145: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.146: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.146: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.146: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.146: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.146: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.146: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.147: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.147: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.147: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.147: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.147: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.147: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.147: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.147: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.148: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.148: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.148: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.148: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.148: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.148: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.149: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.149: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.149: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.149: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.149: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.149: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.150: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.150: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.150: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.150: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.150: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.150: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.151: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.151: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.151: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.151: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.151: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.151: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.152: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.152: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.152: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.152: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.152: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.152: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.153: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.153: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.153: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.153: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.153: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.153: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.154: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.154: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.154: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.154: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.154: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.154: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.155: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.155: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.155: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.155: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.155: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.155: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.156: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.156: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.156: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.156: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.156: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.156: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.157: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.157: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.157: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.157: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.157: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.157: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.158: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.158: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.158: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.158: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.158: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.158: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.159: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.159: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.159: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.159: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.159: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.159: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.160: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.160: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.160: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.160: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.160: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.160: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.161: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.161: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.161: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.161: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.161: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.161: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.162: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.162: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.162: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.162: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.162: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.162: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.163: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.163: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.163: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.163: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.163: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.163: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.163: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.163: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.164: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.164: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.164: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.164: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.164: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.164: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.165: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.165: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.165: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.165: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.165: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.165: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.166: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.166: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.166: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.166: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.166: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.166: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.167: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.167: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.167: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.167: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.167: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.167: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.168: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.168: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.168: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.168: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.168: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.168: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.169: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.169: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.169: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.169: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.169: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.169: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.170: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.170: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.170: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.170: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.170: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.170: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.170: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.171: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.171: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.171: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.171: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.171: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.171: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.171: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.172: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.172: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.172: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.172: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.172: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.173: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.173: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.173: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.173: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.173: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.173: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.174: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.174: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.174: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.174: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.174: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.174: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.175: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.175: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.175: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.175: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.175: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.175: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.176: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.176: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.176: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.176: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.176: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.176: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.176: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.176: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.177: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.177: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.177: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.177: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.177: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.177: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.178: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.178: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.178: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.178: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.178: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.179: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.179: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.179: variance_after = 1435 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.179: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.179: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.179: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.179: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.180: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.180: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.180: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.180: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.180: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.180: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.181: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.181: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.181: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.181: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.181: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.181: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.182: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.182: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.182: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.182: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.182: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.182: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.183: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.183: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.183: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.183: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.183: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.183: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.184: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.184: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.184: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.184: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.184: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.184: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.185: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.185: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.185: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.185: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.185: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.185: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.186: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.186: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.186: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.186: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.186: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.186: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.187: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.187: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.187: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.187: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.187: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.187: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.188: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.188: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.188: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.188: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.188: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.188: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.189: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.189: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.189: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.189: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.189: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.189: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.189: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.189: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.190: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.190: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.190: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.190: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.190: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.190: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.191: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.191: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.191: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.191: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.191: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.191: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.192: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.192: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.192: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.192: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.192: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.192: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.193: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.193: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.193: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.193: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.193: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.193: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.194: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.194: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.194: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.194: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.194: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.194: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.195: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.195: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.195: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.195: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.195: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.195: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.196: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.196: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.196: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.196: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.196: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.196: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.197: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.197: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.197: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.197: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.197: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.197: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.198: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.198: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.198: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.198: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.198: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.198: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.199: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.199: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.199: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.199: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.199: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.199: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.200: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.200: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.200: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.200: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.200: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.200: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.200: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.201: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.201: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.201: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.201: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.201: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.201: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.201: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.201: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.202: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.202: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.202: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.202: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.202: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.202: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.203: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.203: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.203: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.203: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.203: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.203: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.204: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.204: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.204: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.204: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.204: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.204: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.205: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.205: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.205: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.205: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.205: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.205: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.206: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.206: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.206: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.206: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.206: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.206: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.207: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.207: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.207: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.207: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.207: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.207: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.208: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.208: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.208: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.208: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.208: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.208: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.209: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.209: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.209: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.209: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.209: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.209: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.210: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.210: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.210: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.210: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.210: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.210: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.210: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.210: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.211: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.211: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.211: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.211: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.211: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.211: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.212: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.212: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.212: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.212: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.212: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.212: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.213: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.213: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.213: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.213: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.213: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.213: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.214: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.214: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.214: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.214: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.214: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.215: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.215: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.215: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.215: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.215: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.215: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.215: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.216: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.216: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.216: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.216: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.216: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.216: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.217: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.217: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.217: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.217: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.217: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.217: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.217: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.217: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.218: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.218: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.218: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.218: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.218: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.218: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.218: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.218: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.219: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.219: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.219: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.219: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.219: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.219: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.220: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.220: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.220: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.220: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.220: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.220: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.221: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.221: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.221: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.221: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.221: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.221: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.222: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.222: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.222: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.222: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.222: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.222: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.223: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.223: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.223: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.223: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.223: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.223: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.224: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.224: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.224: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.224: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.224: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.224: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.225: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.225: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.225: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.225: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.225: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.225: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.226: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.226: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.226: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.226: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.226: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.226: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.227: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.227: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.227: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.227: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.227: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.227: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.227: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.227: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.228: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.228: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.228: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.228: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.228: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.228: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.229: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.229: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.229: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.229: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.229: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.229: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.230: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.230: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.230: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.230: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.230: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.230: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.231: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.231: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.231: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.231: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.231: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.231: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.232: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.232: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.232: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.232: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.232: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.232: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.233: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.233: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.233: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.233: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.233: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.234: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.234: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.234: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.234: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.234: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.234: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.234: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.235: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.235: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.235: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.235: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.235: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.235: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.236: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.236: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.236: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.236: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.236: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.236: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.237: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.237: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.237: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.237: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.237: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.237: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.237: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.237: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.238: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.238: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.238: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.238: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.238: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.238: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.239: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.239: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.239: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.239: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.239: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.239: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.240: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.240: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.240: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.240: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.240: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.240: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.241: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.241: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.241: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.241: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.241: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.241: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.242: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.242: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.242: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.242: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.242: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.242: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.242: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.242: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.243: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.243: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.243: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.243: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.243: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.244: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.244: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.244: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.244: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.244: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.244: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.245: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.245: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.245: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.245: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.245: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.245: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.246: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.246: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.246: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.246: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.246: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.246: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.247: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.247: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.247: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.247: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.247: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.247: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.247: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.247: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.248: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.248: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.248: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.248: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.249: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.249: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.249: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.249: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.249: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.249: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.250: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.250: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.250: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.250: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.250: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.250: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.250: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.250: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.251: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.251: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.251: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.251: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.251: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.251: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.252: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.252: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.252: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.252: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.252: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.252: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.253: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.253: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.253: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.253: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.253: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.253: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.254: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.254: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.254: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.254: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.254: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.254: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.255: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.255: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.255: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.255: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.255: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.255: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.256: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.256: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.256: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.256: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.256: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.256: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.257: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.257: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.257: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.257: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.257: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.257: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.258: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.258: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.258: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.258: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.258: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.258: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.259: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.259: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.259: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.259: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.259: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.259: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.260: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.260: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.260: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.260: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.260: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.260: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.260: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.260: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.261: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.261: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.261: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.261: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.261: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.261: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.262: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.262: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.262: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.262: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.262: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.262: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.263: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.263: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.263: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.263: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.263: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.263: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.264: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.264: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.264: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.264: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.264: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.264: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.265: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.265: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.265: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.265: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.265: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.265: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.265: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.266: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.266: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.266: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.266: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.266: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.267: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.267: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.267: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.267: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.267: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.267: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.268: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.268: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.268: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.268: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.268: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.268: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.269: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.269: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.269: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.269: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.269: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.269: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.270: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.270: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.270: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.270: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.270: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.270: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.270: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.270: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.271: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.271: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.271: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.271: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.271: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.271: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.272: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.272: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.272: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.272: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.272: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.272: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.273: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.273: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.273: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.273: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.273: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.273: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.274: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.274: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.274: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.274: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.274: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.274: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.275: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.275: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.275: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.275: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.275: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.275: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.276: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.276: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.276: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.276: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.276: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.276: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.277: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.277: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.277: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.277: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.277: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.277: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.278: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.278: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.278: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.278: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.278: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.278: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.278: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.279: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.279: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.279: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.279: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.279: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.279: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.279: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.280: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.280: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.280: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.280: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.280: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.280: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.281: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.281: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.281: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.281: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.281: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.281: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.282: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.282: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.282: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.282: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.282: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.282: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.283: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.283: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.283: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.283: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.283: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.283: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.283: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.284: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.284: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.284: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.284: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.284: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.285: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.285: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.285: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.285: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.285: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.285: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.286: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.286: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.286: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.286: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.286: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.286: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.287: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.287: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.287: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.287: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.287: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.287: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.288: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.288: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.288: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.288: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.288: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.288: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.289: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.289: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.289: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.289: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.289: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.289: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.289: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.289: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.290: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.290: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.290: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.290: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.290: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.290: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.291: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.291: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.291: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.291: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.291: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.291: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.292: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.292: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.292: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.292: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.292: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.292: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.293: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.293: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.293: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.293: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.293: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.293: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.294: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.294: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.294: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.294: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.294: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.294: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.295: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.295: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.295: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.295: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.295: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.295: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.295: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.295: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.296: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.296: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.296: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.296: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.296: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.296: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.297: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.297: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.297: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.297: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.297: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.297: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.298: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.298: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.298: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.298: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.298: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.298: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.299: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.299: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.299: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.299: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.299: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.299: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.299: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.300: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.300: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.300: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.300: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.300: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.301: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.301: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.301: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.301: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.301: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.301: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.302: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.302: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.302: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.302: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.302: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.302: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.303: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.303: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.303: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.303: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.303: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.303: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.304: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.304: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.304: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.304: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.304: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.304: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.304: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.304: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.305: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.305: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.305: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.305: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.305: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.305: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.306: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.306: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.306: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.306: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.306: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.306: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.307: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.307: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.307: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.307: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.307: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.307: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.307: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.308: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.308: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.308: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.308: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.308: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.309: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.309: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.309: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.309: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.309: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.309: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.309: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.310: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.310: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.310: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.310: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.310: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.311: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.311: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.311: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.311: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.311: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.312: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.312: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.312: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.312: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.312: variance_after = 1425 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.312: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.312: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.313: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.313: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.313: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.313: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.313: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.313: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.314: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.314: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.314: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.314: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.314: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.314: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.314: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.314: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.315: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.315: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.315: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.315: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.315: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.315: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.316: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.316: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.316: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.316: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.316: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.316: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.317: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.317: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.317: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.317: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.317: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.317: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.318: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.318: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.318: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.318: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.318: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.318: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.318: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.318: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.319: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.319: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.319: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.319: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.319: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.319: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.320: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.320: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.320: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.320: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.320: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.320: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.321: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.321: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.321: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.321: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.321: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.321: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.322: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.322: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.322: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.322: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.322: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.322: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.322: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.322: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.323: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.323: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.323: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.323: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.323: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.323: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.324: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.324: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.324: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.324: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.324: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.324: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.325: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.325: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.325: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.325: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.325: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.325: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.326: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.326: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.326: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.326: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.326: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.326: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.326: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.326: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.327: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.327: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.327: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.327: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.327: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.327: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.328: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.328: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.328: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.328: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.328: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.328: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.329: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.329: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.329: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.329: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.329: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.329: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.330: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.330: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.330: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.330: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.330: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.330: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.331: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.331: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.331: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.331: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.331: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.331: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.332: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.332: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.332: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.332: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.332: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.332: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.333: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.333: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.333: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.333: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.333: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.333: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.334: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.334: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.334: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.334: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.334: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.334: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.335: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.335: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.335: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.335: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.335: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.335: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.336: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.336: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.336: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.336: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.336: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.336: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.337: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.337: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.337: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.337: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.337: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.337: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.338: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.338: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.338: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.338: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.338: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.338: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.338: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.338: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.339: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.339: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.339: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.339: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.339: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.339: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.340: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.340: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.340: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.340: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.340: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.340: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.341: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.341: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.341: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.341: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.341: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.341: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.342: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.342: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.342: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.342: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.342: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.342: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.343: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.343: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.343: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.343: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.344: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.344: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.344: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.344: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.344: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.344: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.344: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.344: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.345: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.345: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.345: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.345: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.345: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.345: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.346: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.346: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.346: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.346: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.346: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.346: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.347: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.347: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.347: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.347: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.347: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.347: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.348: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.348: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.348: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.348: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.348: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.348: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.349: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.349: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.349: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.349: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.349: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.349: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.350: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.350: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.350: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.350: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.350: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.350: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.350: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.350: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.351: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.351: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.351: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.351: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.351: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.351: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.352: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.352: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.352: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.352: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.352: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.352: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.353: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.353: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.353: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.353: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.353: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.353: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.354: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.354: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.354: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.354: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.354: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.354: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.355: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.355: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.355: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.355: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.355: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.355: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.356: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.356: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.356: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.356: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.356: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.356: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.357: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.357: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.357: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.357: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.357: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.357: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.357: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.357: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.358: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.358: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.358: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.358: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.358: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.358: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.359: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.359: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.359: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.359: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.359: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.359: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.360: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.360: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.360: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.360: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.360: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.360: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.361: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.361: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.361: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.361: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.361: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.361: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.362: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.362: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.362: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.362: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.362: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.362: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.363: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.363: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.363: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.363: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.363: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.363: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.364: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.364: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.364: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.364: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.364: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.364: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.365: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.365: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.365: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.365: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.365: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.365: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.366: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.366: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.366: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.366: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.366: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.366: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.366: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.366: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.367: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.367: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.367: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.367: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.367: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.367: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.368: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.368: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.368: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.368: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.368: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.368: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.369: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.369: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.369: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.369: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.369: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.369: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.370: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.370: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.370: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.370: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.370: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.370: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.370: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.371: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.371: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.371: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.371: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.371: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.372: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.372: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.372: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.372: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.372: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.373: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.373: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.373: variance_after = 1532 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.373: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.373: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.373: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.373: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.374: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.374: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.374: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.374: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.374: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.374: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.375: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.375: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.375: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.375: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.375: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.375: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.376: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.376: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.376: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.376: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.377: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.377: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.377: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.377: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.377: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.377: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.378: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.378: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.378: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.378: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.378: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.378: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.378: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.378: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.379: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.379: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.379: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.379: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.379: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.379: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.380: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.380: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.380: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.380: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.380: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.380: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.381: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.381: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.381: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.381: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.381: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.381: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.382: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.382: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.382: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.382: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.382: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.382: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.383: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.383: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.383: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.383: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.383: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.383: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.384: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.384: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.384: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.384: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.384: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.384: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.385: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.385: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.385: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.385: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.385: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.385: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.386: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.386: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.386: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.386: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.386: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.386: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.387: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.387: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.387: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.387: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.387: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.387: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.388: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.388: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.388: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.388: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.388: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.388: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.389: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.389: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.389: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.389: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.389: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.389: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.390: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.390: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.390: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.390: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.390: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.390: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.390: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.390: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.391: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.391: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.391: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.391: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.391: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.391: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.392: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.392: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.392: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.392: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.392: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.392: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.393: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.393: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.393: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.393: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.393: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.393: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.394: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.394: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.394: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.394: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.394: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.394: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.395: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.395: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.395: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.395: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.395: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.395: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.396: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.396: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.396: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.396: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.396: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.396: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.396: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.396: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.397: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.397: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.397: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.397: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.397: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.397: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.398: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.398: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.398: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.398: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.398: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.398: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.399: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.399: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.399: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.399: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.399: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.399: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.400: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.400: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.400: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.400: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.400: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.400: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.401: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.401: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.401: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.401: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.401: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.401: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.402: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.402: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.402: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.402: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.402: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.402: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.403: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.403: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.403: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.403: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.403: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.403: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.404: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.404: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.404: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.404: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.404: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.404: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.405: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.405: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.405: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.405: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.405: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.405: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.406: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.406: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.406: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.406: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.406: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.406: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.407: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.407: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.407: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.407: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.407: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.407: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.407: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.407: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.408: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.408: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.408: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.408: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.408: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.408: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.408: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.409: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.409: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.409: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.409: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.409: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.409: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.409: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.409: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.410: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.410: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.410: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.410: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.410: variance_after = 1691 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.410: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.410: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.411: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.411: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.411: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.411: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.411: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.411: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.412: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.412: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.412: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.412: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.412: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.412: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.413: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.413: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.413: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.413: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.413: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.413: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.413: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.413: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.414: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.414: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.414: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.414: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.414: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.414: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.415: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.415: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.415: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.415: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.415: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.415: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.416: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.416: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.416: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.416: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.416: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.416: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.416: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.417: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.417: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.417: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.417: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.418: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.418: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.418: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.418: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.418: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.418: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.418: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.418: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.419: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.419: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.419: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.419: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.419: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.419: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.419: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.419: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.420: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.420: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.420: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.420: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.420: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.420: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.421: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.421: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.421: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.421: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.421: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.421: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.422: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.422: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.422: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.422: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.422: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.422: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.423: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.423: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.423: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.423: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.423: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.423: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.424: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.424: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.424: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.424: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.424: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.424: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.425: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.425: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.425: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.425: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.425: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.425: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.425: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.425: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.426: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.426: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.426: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.426: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.426: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.426: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.427: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.427: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.427: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.427: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.427: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.427: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.427: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.427: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.428: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.428: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.428: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.428: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.428: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.428: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.428: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.428: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.429: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.429: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.429: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.429: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.429: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.429: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.430: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.430: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.430: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.430: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.430: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.430: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.431: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.431: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.431: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.431: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.431: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.431: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.431: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.431: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.432: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.432: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.432: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.432: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.432: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.432: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.433: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.433: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.433: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.433: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.433: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.433: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.434: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.434: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.434: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.434: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.434: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.434: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.435: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.435: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.435: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.435: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.435: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.435: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.436: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.436: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.436: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.436: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.436: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.436: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.437: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.437: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.437: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.437: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.437: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.437: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.437: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.437: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.438: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.438: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.438: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.438: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.438: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.438: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.439: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.439: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.439: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.439: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.439: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.439: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.440: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.440: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.440: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.440: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.440: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.440: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.441: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.441: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.441: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.441: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.441: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.441: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.442: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.442: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.442: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.442: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.442: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.442: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.443: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.443: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.443: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.443: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.443: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.443: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.444: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.444: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.444: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.444: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.444: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.444: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.445: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.445: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.445: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.445: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.445: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.445: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.445: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.446: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.446: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.446: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.446: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.446: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.446: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.446: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.447: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.447: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.447: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.447: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.447: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.448: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.448: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.448: variance_after = 1845 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.448: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.448: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.448: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.448: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.449: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.449: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.449: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.449: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.449: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.449: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.450: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.450: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.450: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.450: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.450: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.450: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.451: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.451: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.451: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.451: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.451: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.451: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.452: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.452: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.452: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.452: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.452: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.452: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.453: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.453: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.453: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.453: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.453: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.453: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.454: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.454: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.454: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.454: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.454: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.454: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.455: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.455: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.455: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.455: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.455: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.455: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.456: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.456: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.457: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.457: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.457: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.457: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.457: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.457: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.458: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.458: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.458: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.458: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.458: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.458: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.459: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.459: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.459: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.459: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.459: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.459: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.460: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.460: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.460: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.460: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.460: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.460: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.461: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.461: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.461: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.461: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.461: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.461: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.462: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.462: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.462: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.462: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.462: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.462: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.463: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.463: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.463: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.463: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.463: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.463: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.464: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.464: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.464: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.464: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.464: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.464: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.465: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.465: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.465: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.465: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.465: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.465: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.465: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.465: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.466: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.466: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.466: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.466: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.466: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.466: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.467: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.467: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.467: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.467: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.467: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.467: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.468: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.468: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.468: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.468: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.468: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.468: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.469: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.469: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.469: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.469: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.469: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.469: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.470: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.470: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.470: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.470: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.470: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.470: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.471: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.471: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.471: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.471: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.471: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.471: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.472: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.472: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.472: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.472: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.472: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.472: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.473: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.473: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.473: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.473: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.473: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.473: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.474: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.474: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.474: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.474: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.474: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.474: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.474: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.474: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.475: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.475: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.475: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.475: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.475: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.475: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.476: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.476: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.476: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.476: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.476: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.476: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.477: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.477: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.477: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.477: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.477: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.477: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.478: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.478: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.478: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.478: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.478: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.478: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.479: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.479: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.479: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.479: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.479: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.479: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.480: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.480: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.480: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.480: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.480: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.480: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.481: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.481: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.481: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.481: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.481: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.481: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.482: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.482: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.482: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.482: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.482: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.482: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.483: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.483: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.483: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.483: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.483: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.483: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.484: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.484: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.484: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.484: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.484: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.484: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.485: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.485: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.485: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.485: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.485: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.485: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.486: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.486: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.486: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.486: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.486: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.486: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.487: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.487: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.487: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.487: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.487: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.487: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.488: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.488: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.488: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.488: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.488: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.488: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.489: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.489: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.489: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.489: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.489: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.489: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.489: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.489: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.490: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.490: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.490: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.490: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.490: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.490: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.490: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.491: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.491: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.491: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.491: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.491: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.491: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.491: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.492: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.492: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.492: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.492: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.492: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.493: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.493: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.493: variance_after = 2342 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.493: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.493: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.493: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.493: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.494: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.494: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.494: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.494: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.494: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.494: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.495: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.495: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.495: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.495: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.495: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.495: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.496: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.496: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.496: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.496: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.496: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.496: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.496: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.496: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.497: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.497: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.497: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.497: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.497: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.497: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.498: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.498: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.498: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.498: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.498: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.498: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.499: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.499: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.499: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.499: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.499: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.499: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.500: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.500: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.500: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.500: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.500: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.500: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.500: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.500: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.501: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.501: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.501: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.501: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.501: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.501: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.502: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.502: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.502: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.502: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.502: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.502: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.503: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.503: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.503: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.503: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.503: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.503: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.504: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.504: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.504: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.504: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.504: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.504: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.505: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.505: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.505: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.505: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.505: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.505: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.506: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.506: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.506: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.506: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.506: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.506: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.507: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.507: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.507: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.507: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.507: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.507: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.508: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.508: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.508: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.508: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.508: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.508: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.508: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.508: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.509: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.509: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.509: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.509: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.509: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.509: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.510: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.510: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.510: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.510: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.510: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.510: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.511: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.511: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.511: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.511: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.511: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.511: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.512: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.512: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.512: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.512: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.512: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.512: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.513: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.513: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.513: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.513: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.513: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.513: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.513: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.513: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.514: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.514: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.514: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.514: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.514: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.514: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.515: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.515: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.515: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.515: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.516: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.516: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.516: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.516: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.516: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.516: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.516: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.516: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.517: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.517: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.517: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.517: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.517: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.517: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.518: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.518: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.518: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.518: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.518: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.518: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.519: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.519: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.519: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.519: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.519: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.519: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.519: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.520: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.520: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.520: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.520: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.520: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.520: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.520: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.521: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.521: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.521: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.521: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.521: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.521: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.522: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.522: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.522: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.522: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.522: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.523: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.523: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.523: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.523: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.523: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.523: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.523: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.524: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.524: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.524: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.524: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.525: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.525: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.525: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.525: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.525: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.525: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.526: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.526: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.526: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.526: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.526: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.526: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.527: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.527: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.527: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.527: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.527: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.527: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.528: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.528: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.528: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.528: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.528: [vfs7552] QUERY DATA READY entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.528: Sending vfs7552_is_image_ready 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.529: [vfs7552] QUERY DATA READY entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.529: Receiving 64 bytes 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.529: Got 6 bytes out of 64 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.529: [vfs7552] QUERY DATA READY completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.529: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.529: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.529: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.529: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.529: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.530: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.530: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.530: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.530: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.530: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.531: [vfs7552] CAPTURE_NUM_STATES entering state 2 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.531: [vfs7552] REQUEST CHUNK entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.531: Sending vfs7552_read_image_chunk 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.531: [vfs7552] REQUEST CHUNK completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.531: [vfs7552] CAPTURE_NUM_STATES entering state 3 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.532: [vfs7552] CAPTURE_NUM_STATES entering state 4 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.532: Cleaning image 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.532: variance_after = 16 192s 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.532: [vfs7552] CAPTURE_NUM_STATES completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.532: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.542: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.542: [vfs7552] STOP CAPTURE entering state 0 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.542: Sending vfs7552_cmd_04 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.542: [vfs7552] STOP CAPTURE entering state 1 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.543: Receiving 64 bytes 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.543: [vfs7552] STOP CAPTURE entering state 2 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.543: Sending vfs7552_cmd_52 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.544: [vfs7552] STOP CAPTURE entering state 3 192s (process:4246): libfprint-vfs7552-DEBUG: 20:26:40.544: Receiving 64 bytes 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.544: [vfs7552] STOP CAPTURE completed successfully 192s (process:4246): libfprint-SSM-DEBUG: 20:26:40.544: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 192s (process:4246): libfprint-device-DEBUG: 20:26:40.544: Device reported finger status change: FP_FINGER_STATUS_NONE 192s (process:4246): libfprint-image_device-DEBUG: 20:26:40.544: Image device reported finger status: off 192s (process:4246): libfprint-image_device-DEBUG: 20:26:40.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 192s (process:4246): libfprint-image_device-DEBUG: 20:26:40.544: Deactivating image device 192s (process:4246): libfprint-image_device-DEBUG: 20:26:40.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 192s (process:4246): libfprint-image_device-DEBUG: 20:26:40.544: Image device deactivation completed 192s (process:4246): libfprint-image_device-DEBUG: 20:26:40.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 192s (process:4246): libfprint-device-DEBUG: 20:26:40.544: Device reported capture completion 192s (process:4246): libfprint-device-DEBUG: 20:26:40.544: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 192s (process:4246): libfprint-device-DEBUG: 20:26:40.544: Updated temperature model after 2.36 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 192s (process:4246): libfprint-image_device-DEBUG: 20:26:40.545: Image device close completed 192s (process:4246): libfprint-device-DEBUG: 20:26:40.545: Device reported close completion 192s (process:4246): libfprint-device-DEBUG: 20:26:40.545: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s (process:4246): libfprint-device-DEBUG: 20:26:40.545: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 192s ** (umockdev-run:4242): DEBUG: 20:26:40.600: umockdev.vala:154: Removing test bed /tmp/umockdev.U6FJ22 192s (umockdev-run:4242): GLib-DEBUG: 20:26:40.606: unsetenv() is not thread-safe and should not be used after threads are created 192s Comparing PNGs /tmp/libfprint-umockdev-test-9b35a_ww/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 192s PASS: libfprint-2/driver-vfs7552.test 192s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.94.3.test 192s TAP version 14 192s # random seed: R02Se74ab8b0029e4b1e9f80f6f63c8a114b 192s 1..14 192s # Start of device tests 192s # Start of async tests 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 1 /device/async/open 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 2 /device/async/close 192s # End of async tests 192s # Start of sync tests 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 3 /device/sync/open 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 4 /device/sync/close 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 5 /device/sync/get_driver 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 6 /device/sync/get_device_id 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 7 /device/sync/get_name 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 8 /device/sync/get_scan_type 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 9 /device/sync/get_nr_enroll_stages 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 10 /device/sync/supports_identify 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 11 /device/sync/supports_capture 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 12 /device/sync/has_storage 192s # Start of open tests 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 13 /device/sync/open/notify 192s # End of open tests 192s # Start of close tests 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f602209d3, GType is 99083936700288 192s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 192s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 192s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x763f6021ab7b, GType is 99083936704960 192s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 192s # libfprint-context-DEBUG: created 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 192s # 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 192s # 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 192s # 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s ok 14 /device/sync/close/notify 192s # End of close tests 192s # End of sync tests 192s # End of device tests 192s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.94.3.test 192s Running test: libfprint-2/fp-device.test 192s TAP version 14 192s # random seed: R02S1ca0589a776f3df863cc551549ca37b3 192s 1..17 192s # Start of device tests 192s # Start of async tests 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-GWEC22/virtual_image.socket 192s # libfprint-context-DEBUG: created 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:40.654: 160450178: ../libfprint/drivers/virtual-image.c:216 192s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:40.654: 160450242: ../libfprint/drivers/virtual-device-listener.c:153 192s # libfprint-image_device-DEBUG: Image device open completed 192s # libfprint-device-DEBUG: Device reported open completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:40.755: 160550756: ../libfprint/drivers/virtual-image.c:244 192s # libfprint-image_device-DEBUG: Image device close completed 192s # libfprint-device-DEBUG: Device reported close completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 192s ok 1 /device/async/open 192s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 192s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 192s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 192s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FWAJ22/virtual_image.socket 192s # libfprint-context-DEBUG: created 192s # libfprint-device-DEBUG: Device reported probe completion 192s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 192s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 192s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:40.856: 160652493: ../libfprint/drivers/virtual-image.c:216 192s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:40.856: 160652522: ../libfprint/drivers/virtual-device-listener.c:153 193s # libfprint-image_device-DEBUG: Image device open completed 193s # libfprint-device-DEBUG: Device reported open completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:40.957: 160752871: ../libfprint/drivers/virtual-image.c:244 193s # libfprint-image_device-DEBUG: Image device close completed 193s # libfprint-device-DEBUG: Device reported close completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 193s ok 2 /device/async/close 193s # End of async tests 193s # Start of sync tests 193s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 193s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 193s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 193s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LOTZ12/virtual_image.socket 193s # libfprint-context-DEBUG: created 193s # libfprint-device-DEBUG: Device reported probe completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.058: 160854158: ../libfprint/drivers/virtual-image.c:216 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:41.058: 160854173: ../libfprint/drivers/virtual-device-listener.c:153 193s # libfprint-image_device-DEBUG: Image device open completed 193s # libfprint-device-DEBUG: Device reported open completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.158: 160954545: ../libfprint/drivers/virtual-image.c:244 193s # libfprint-image_device-DEBUG: Image device close completed 193s # libfprint-device-DEBUG: Device reported close completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 193s ok 3 /device/sync/open 193s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 193s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 193s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 193s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-F0Y312/virtual_image.socket 193s # libfprint-context-DEBUG: created 193s # libfprint-device-DEBUG: Device reported probe completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.260: 161055777: ../libfprint/drivers/virtual-image.c:216 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:41.260: 161055795: ../libfprint/drivers/virtual-device-listener.c:153 193s # libfprint-image_device-DEBUG: Image device open completed 193s # libfprint-device-DEBUG: Device reported open completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.360: 161156094: ../libfprint/drivers/virtual-image.c:244 193s # libfprint-image_device-DEBUG: Image device close completed 193s # libfprint-device-DEBUG: Device reported close completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 193s ok 4 /device/sync/close 193s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 193s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 193s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 193s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-M4TA22/virtual_image.socket 193s # libfprint-context-DEBUG: created 193s # libfprint-device-DEBUG: Device reported probe completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.461: 161257310: ../libfprint/drivers/virtual-image.c:216 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:41.461: 161257325: ../libfprint/drivers/virtual-device-listener.c:153 193s # libfprint-image_device-DEBUG: Image device open completed 193s # libfprint-device-DEBUG: Device reported open completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.562: 161357663: ../libfprint/drivers/virtual-image.c:244 193s # libfprint-image_device-DEBUG: Image device close completed 193s # libfprint-device-DEBUG: Device reported close completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 193s ok 5 /device/sync/get_driver 193s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 193s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 193s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 193s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-HKZE22/virtual_image.socket 193s # libfprint-context-DEBUG: created 193s # libfprint-device-DEBUG: Device reported probe completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.663: 161458990: ../libfprint/drivers/virtual-image.c:216 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:41.663: 161459029: ../libfprint/drivers/virtual-device-listener.c:153 193s # libfprint-image_device-DEBUG: Image device open completed 193s # libfprint-device-DEBUG: Device reported open completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.763: 161559275: ../libfprint/drivers/virtual-image.c:244 193s # libfprint-image_device-DEBUG: Image device close completed 193s # libfprint-device-DEBUG: Device reported close completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 193s ok 6 /device/sync/get_device_id 193s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 193s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 193s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 193s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-NJ4I22/virtual_image.socket 193s # libfprint-context-DEBUG: created 193s # libfprint-device-DEBUG: Device reported probe completion 193s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 193s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.864: 161660454: ../libfprint/drivers/virtual-image.c:216 193s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:41.864: 161660466: ../libfprint/drivers/virtual-device-listener.c:153 194s # libfprint-image_device-DEBUG: Image device open completed 194s # libfprint-device-DEBUG: Device reported open completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:41.965: 161760729: ../libfprint/drivers/virtual-image.c:244 194s # libfprint-image_device-DEBUG: Image device close completed 194s # libfprint-device-DEBUG: Device reported close completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 194s ok 7 /device/sync/get_name 194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-FCG212/virtual_image.socket 194s # libfprint-context-DEBUG: created 194s # libfprint-device-DEBUG: Device reported probe completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.066: 161861782: ../libfprint/drivers/virtual-image.c:216 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:42.066: 161861800: ../libfprint/drivers/virtual-device-listener.c:153 194s # libfprint-image_device-DEBUG: Image device open completed 194s # libfprint-device-DEBUG: Device reported open completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.166: 161962147: ../libfprint/drivers/virtual-image.c:244 194s Executing: libfprint-2/fp-device.test 194s # libfprint-image_device-DEBUG: Image device close completed 194s # libfprint-device-DEBUG: Device reported close completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 194s ok 8 /device/sync/get_scan_type 194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-YDL612/virtual_image.socket 194s # libfprint-context-DEBUG: created 194s # libfprint-device-DEBUG: Device reported probe completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.268: 162063660: ../libfprint/drivers/virtual-image.c:216 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:42.268: 162063680: ../libfprint/drivers/virtual-device-listener.c:153 194s # libfprint-image_device-DEBUG: Image device open completed 194s # libfprint-device-DEBUG: Device reported open completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.368: 162164068: ../libfprint/drivers/virtual-image.c:244 194s # libfprint-image_device-DEBUG: Image device close completed 194s # libfprint-device-DEBUG: Device reported close completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 194s ok 9 /device/sync/get_finger_status 194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-PTNA22/virtual_image.socket 194s # libfprint-context-DEBUG: created 194s # libfprint-device-DEBUG: Device reported probe completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.469: 162265376: ../libfprint/drivers/virtual-image.c:216 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:42.469: 162265393: ../libfprint/drivers/virtual-device-listener.c:153 194s # libfprint-image_device-DEBUG: Image device open completed 194s # libfprint-device-DEBUG: Device reported open completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.570: 162365679: ../libfprint/drivers/virtual-image.c:244 194s # libfprint-image_device-DEBUG: Image device close completed 194s # libfprint-device-DEBUG: Device reported close completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 194s ok 10 /device/sync/get_nr_enroll_stages 194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-V0SE22/virtual_image.socket 194s # libfprint-context-DEBUG: created 194s # libfprint-device-DEBUG: Device reported probe completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.671: 162466768: ../libfprint/drivers/virtual-image.c:216 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:42.671: 162466780: ../libfprint/drivers/virtual-device-listener.c:153 194s # libfprint-image_device-DEBUG: Image device open completed 194s # libfprint-device-DEBUG: Device reported open completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.771: 162567139: ../libfprint/drivers/virtual-image.c:244 194s # libfprint-image_device-DEBUG: Image device close completed 194s # libfprint-device-DEBUG: Device reported close completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 194s ok 11 /device/sync/supports_identify 194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-05XI22/virtual_image.socket 194s # libfprint-context-DEBUG: created 194s # libfprint-device-DEBUG: Device reported probe completion 194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.872: 162668293: ../libfprint/drivers/virtual-image.c:216 194s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:42.872: 162668309: ../libfprint/drivers/virtual-device-listener.c:153 195s # libfprint-image_device-DEBUG: Image device open completed 195s # libfprint-device-DEBUG: Device reported open completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:42.973: 162768635: ../libfprint/drivers/virtual-image.c:244 195s # libfprint-image_device-DEBUG: Image device close completed 195s # libfprint-device-DEBUG: Device reported close completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 195s ok 12 /device/sync/supports_capture 195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-5UC212/virtual_image.socket 195s # libfprint-context-DEBUG: created 195s # libfprint-device-DEBUG: Device reported probe completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.074: 162869834: ../libfprint/drivers/virtual-image.c:216 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:43.074: 162869855: ../libfprint/drivers/virtual-device-listener.c:153 195s # libfprint-image_device-DEBUG: Image device open completed 195s # libfprint-device-DEBUG: Device reported open completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.174: 162970231: ../libfprint/drivers/virtual-image.c:244 195s # libfprint-image_device-DEBUG: Image device close completed 195s # libfprint-device-DEBUG: Device reported close completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 195s ok 13 /device/sync/has_storage 195s # Start of open tests 195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-M1E612/virtual_image.socket 195s # libfprint-context-DEBUG: created 195s # libfprint-device-DEBUG: Device reported probe completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.276: 163071801: ../libfprint/drivers/virtual-image.c:216 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:43.276: 163071829: ../libfprint/drivers/virtual-device-listener.c:153 195s # libfprint-image_device-DEBUG: Image device open completed 195s # libfprint-device-DEBUG: Device reported open completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.376: 163172218: ../libfprint/drivers/virtual-image.c:244 195s # libfprint-image_device-DEBUG: Image device close completed 195s # libfprint-device-DEBUG: Device reported close completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 195s ok 14 /device/sync/open/notify 195s # End of open tests 195s # Start of close tests 195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LKHA22/virtual_image.socket 195s # libfprint-context-DEBUG: created 195s # libfprint-device-DEBUG: Device reported probe completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.478: 163273664: ../libfprint/drivers/virtual-image.c:216 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:43.478: 163273689: ../libfprint/drivers/virtual-device-listener.c:153 195s # libfprint-image_device-DEBUG: Image device open completed 195s # libfprint-device-DEBUG: Device reported open completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.578: 163374055: ../libfprint/drivers/virtual-image.c:244 195s # libfprint-image_device-DEBUG: Image device close completed 195s # libfprint-device-DEBUG: Device reported close completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 195s ok 15 /device/sync/close/notify 195s # End of close tests 195s # Start of identify tests 195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LWME22/virtual_image.socket 195s # libfprint-context-DEBUG: created 195s # libfprint-device-DEBUG: Device reported probe completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.679: 163475420: ../libfprint/drivers/virtual-image.c:216 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:43.679: 163475437: ../libfprint/drivers/virtual-device-listener.c:153 195s # libfprint-image_device-DEBUG: Image device open completed 195s # libfprint-device-DEBUG: Device reported open completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.780: 163575789: ../libfprint/drivers/virtual-image.c:244 195s # libfprint-image_device-DEBUG: Image device close completed 195s # libfprint-device-DEBUG: Device reported close completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 195s ok 16 /device/sync/identify/cancelled 195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1?: No such file or directory 195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ZZOI22/virtual_image.socket 195s # libfprint-context-DEBUG: created 195s # libfprint-device-DEBUG: Device reported probe completion 195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.881: 163677207: ../libfprint/drivers/virtual-image.c:216 195s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_device_connection-DEBUG: 20:26:43.881: 163677229: ../libfprint/drivers/virtual-device-listener.c:153 196s # libfprint-image_device-DEBUG: Image device open completed 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:4285): libfprint-virtual_image-DEBUG: 20:26:43.981: 163777600: ../libfprint/drivers/virtual-image.c:244 196s # libfprint-image_device-DEBUG: Image device close completed 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 196s ok 17 /device/sync/identify/null-prints 196s # End of identify tests 196s # End of sync tests 196s # End of device tests 196s PASS: libfprint-2/fp-device.test 196s Running test: libfprint-2/fpi-assembling.test 196s TAP version 14 196s # random seed: R02S13c09a4703c6088b92063379adcc5718 196s 1..1 196s # Start of assembling tests 196s # libfprint-assembling-DEBUG: calc delta completed in 0.102441 secs 196s # libfprint-assembling-DEBUG: calc delta completed in 0.076298 secs 196s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 196s # libfprint-assembling-DEBUG: calc delta completed in 0.071945 secs 196s # libfprint-assembling-DEBUG: height is 310 196s ok 1 /assembling/frames 196s # End of assembling tests 196s PASS: libfprint-2/fpi-assembling.test 196s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.94.3.test 196s TAP version 14 196s # random seed: R02S946bb35097042e6eba4050320ca59229 196s 1..4 196s # Start of context tests 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x72f31899b9d3, GType is 109557598535056 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x72f318995b7b, GType is 109557598539728 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 196s ok 1 /context/new 196s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 196s ok 2 /context/no-devices 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x72f31899b9d3, GType is 109557598535056 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x72f318995b7b, GType is 109557598539728 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 196s # 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 196s # 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 196s # 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 3 /context/has-virtual-device 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-ssm-test-v1+1.94.3-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x72f31899b9d3, GType is 109557598535056 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.3 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.3/libdevice-fake-tod-test-driver-v1+1.94.3-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x72f318995b7b, GType is 109557598539728 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.3 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-fake_test_dev_tod_v1+1.94.3-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 196s # 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 4 /context/enumerates-new-devices 196s # End of context tests 196s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.94.3.test 196s Running test: libfprint-2/driver-goodixmoc.test 196s ** (umockdev-run:4339): DEBUG: 20:26:44.392: umockdev.vala:127: Created udev test bed /tmp/umockdev.K1P612 196s ** (umockdev-run:4339): DEBUG: 20:26:44.392: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 196s ** (umockdev-run:4339): DEBUG: 20:26:44.394: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 196s ** (umockdev-run:4339): DEBUG: 20:26:44.399: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.K1P612/dev/bus/usb/003/004 196s ** (umockdev-run:4339): DEBUG: 20:26:44.399: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 196s ** (umockdev-run:4339): DEBUG: 20:26:44.400: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 196s ** (umockdev-run:4339): DEBUG: 20:26:44.403: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.K1P612/dev/bus/usb/003/001 196s ** (umockdev-run:4339): DEBUG: 20:26:44.403: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 196s ** (umockdev-run:4339): DEBUG: 20:26:44.403: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 196s (process:4343): libfprint-context-DEBUG: 20:26:44.478: Initializing FpContext (libfprint version 1.94.8+tod1) 196s (process:4343): libfprint-tod-DEBUG: 20:26:44.478: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 196s (process:4343): libfprint-context-DEBUG: 20:26:44.479: No driver found for USB device 1D6B:0002 196s (process:4343): libfprint-device-DEBUG: 20:26:44.481: Device reported probe completion 196s (process:4343): libfprint-device-DEBUG: 20:26:44.481: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.481: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.482: [goodixmoc] FP_INIT_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.482: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.482: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.483: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.483: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.484: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.484: Firmware type: APP 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.484: Firmware version: 01000274 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.484: [goodixmoc] FP_INIT_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.484: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.485: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.485: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.485: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.486: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.486: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.487: [goodixmoc] FP_INIT_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.487: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.487: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.487: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.487: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.488: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.488: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.489: [goodixmoc] FP_INIT_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.489: Device reported open completion 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.489: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.489: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.489: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.489: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.489: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.490: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.490: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.491: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.491: Successfully cleared storage 196s (process:4343): libfprint-device-DEBUG: 20:26:44.491: Device reported deletion completion 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.491: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.491: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.491: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.492: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.492: [goodixmoc] enroll entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.492: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.492: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.492: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.493: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.493: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.494: [goodixmoc] enroll entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.494: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.494: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.495: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.495: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.495: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.496: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.496: [goodixmoc] enroll entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.496: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.496: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.497: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.497: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.497: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.498: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.498: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-device-DEBUG: 20:26:44.498: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.498: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.498: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.499: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.499: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.500: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.500: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.500: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.500: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.501: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.501: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.501: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.502: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.502: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.502: Device reported enroll progress, reported 1 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.503: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.503: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.503: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.503: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.503: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.504: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.504: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.505: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.505: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.505: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.505: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.506: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.506: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.507: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.507: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.507: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.507: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.507: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.508: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.508: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.508: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.509: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.509: Device reported enroll progress, reported 2 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.509: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.509: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.510: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.510: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.510: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.510: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.511: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.511: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.511: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.512: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.512: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.512: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.513: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.513: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.513: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.513: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.513: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.514: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.514: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.514: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.515: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.515: Device reported enroll progress, reported 3 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.515: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.515: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.515: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.516: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.516: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.516: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.517: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.517: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.517: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.517: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.517: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.517: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.518: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.518: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.519: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.519: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.519: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.519: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.520: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.520: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.520: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.521: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.521: Device reported enroll progress, reported 4 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.521: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.521: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.521: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.522: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.522: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.522: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.523: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.523: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.523: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.523: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.524: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.524: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.524: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.525: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.525: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.525: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.525: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.525: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.526: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.526: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.526: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.527: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.527: Device reported enroll progress, reported 5 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.527: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.527: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.527: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.528: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.528: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.528: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.529: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.529: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.529: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.529: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.529: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.530: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.530: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.530: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.531: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.531: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.531: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.531: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.531: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.532: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.532: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.532: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.533: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.533: Device reported enroll progress, reported 6 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.533: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.533: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.534: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.534: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.534: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.534: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.535: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.535: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.535: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.535: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.535: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.536: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.536: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.536: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.537: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.537: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.537: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.537: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.537: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.538: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.538: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.538: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.539: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.539: Device reported enroll progress, reported 7 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.539: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.539: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.540: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.540: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.540: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.541: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.541: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.541: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.541: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.541: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.542: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.542: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.542: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.543: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.543: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.543: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.543: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.543: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.544: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.544: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.544: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.545: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.545: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.545: Device reported enroll progress, reported 8 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.545: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.545: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.546: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.546: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.546: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.546: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.547: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.547: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.547: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.547: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.548: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.548: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.548: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.549: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.549: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.549: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.549: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.549: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.550: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.550: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.550: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.550: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.551: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.551: Device reported enroll progress, reported 9 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.551: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.551: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.551: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.552: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.552: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.552: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.553: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.553: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.553: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.553: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.553: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.553: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.554: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.554: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.555: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.555: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.555: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.555: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.555: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.555: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.556: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.556: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.557: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.557: Device reported enroll progress, reported 10 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.557: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.557: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.557: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.557: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.558: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.558: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.559: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.559: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.559: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.559: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.559: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.559: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.560: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.560: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.561: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.561: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.561: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.561: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.561: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.561: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.562: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.562: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.562: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.563: Device reported enroll progress, reported 11 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.563: [goodixmoc] enroll entering state 5 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.563: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.563: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.563: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.564: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.564: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.564: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.565: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.565: [goodixmoc] enroll entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.565: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.565: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.565: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.566: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.566: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.566: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.567: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.567: [goodixmoc] enroll entering state 4 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.567: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.567: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.567: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.568: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.568: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.569: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.569: Device reported enroll progress, reported 12 of 12 have been completed 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.569: [goodixmoc] enroll entering state 6 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.569: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.570: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.570: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.570: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.571: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.571: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.572: [goodixmoc] enroll entering state 7 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.572: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.572: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.572: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.572: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.573: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.573: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.573: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.574: [goodixmoc] enroll entering state 8 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.574: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.574: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.574: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.575: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.575: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.575: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.576: [goodixmoc] enroll completed successfully 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.576: Enrollment complete! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.576: Device reported enroll completion 196s (process:4343): libfprint-device-DEBUG: 20:26:44.576: Device reported finger status change: FP_FINGER_STATUS_NONE 196s (process:4343): libfprint-device-DEBUG: 20:26:44.576: Print for finger FP_FINGER_UNKNOWN enrolled 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.576: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.576: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.576: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.576: 164371914: ../libfprint/drivers/goodixmoc/goodix.c:1539 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.576: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.576: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.577: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.577: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.577: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.578: Query complete! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.578: Device reported listing completion 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.578: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.578: Completing action FPI_DEVICE_ACTION_LIST in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.578: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.578: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.578: [goodixmoc] verify entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.578: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.578: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.579: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.579: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.580: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.580: [goodixmoc] verify entering state 1 196s (process:4343): libfprint-device-DEBUG: 20:26:44.580: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.580: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.580: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.581: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.581: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.581: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.582: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.582: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.582: [goodixmoc] verify entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.582: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.582: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.583: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.583: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.583: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.584: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-DEBUG: 20:26:44.584: match, score: 28, study: 0 196s (process:4343): libfprint-device-DEBUG: 20:26:44.584: Device reported verify result 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.584: [goodixmoc] verify entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.584: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.584: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.585: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.585: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.586: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.586: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.586: [goodixmoc] verify completed successfully 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.586: Verify complete! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.586: Device reported verify completion 196s (process:4343): libfprint-device-DEBUG: 20:26:44.586: Device reported finger status change: FP_FINGER_STATUS_NONE 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.586: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.586: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.586: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.587: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.587: [goodixmoc] verify entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.587: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.587: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.588: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.588: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.588: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.589: [goodixmoc] verify entering state 1 196s (process:4343): libfprint-device-DEBUG: 20:26:44.589: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.589: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.589: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.589: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.590: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.590: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.591: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-device-DEBUG: 20:26:44.591: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.591: [goodixmoc] verify entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.591: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.591: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.592: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.592: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.592: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.593: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-DEBUG: 20:26:44.593: match, score: 35, study: 0 196s (process:4343): libfprint-device-DEBUG: 20:26:44.593: Device reported identify result 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.593: [goodixmoc] verify entering state 3 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.593: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.594: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.594: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.594: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.595: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.595: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.596: [goodixmoc] verify completed successfully 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.596: Verify complete! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.596: Device reported identify completion 196s (process:4343): libfprint-device-DEBUG: 20:26:44.596: Device reported finger status change: FP_FINGER_STATUS_NONE 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.596: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.596: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.596: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.596: [goodixmoc] FP_CMD_NUM_STATES entering state 0 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.597: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.597: [goodixmoc] FP_CMD_NUM_STATES entering state 1 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.597: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.598: [goodixmoc] FP_CMD_NUM_STATES entering state 2 196s (process:4343): libfprint-goodixmoc-DEBUG: 20:26:44.598: Successfully deleted enrolled user 196s (process:4343): libfprint-device-DEBUG: 20:26:44.598: Device reported deletion completion 196s (process:4343): libfprint-SSM-DEBUG: 20:26:44.599: [goodixmoc] FP_CMD_NUM_STATES completed successfully 196s (process:4343): libfprint-device-DEBUG: 20:26:44.599: Completing action FPI_DEVICE_ACTION_DELETE in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.599: Not updating temperature model, device can run continuously! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.599: Device reported close completion 196s (process:4343): libfprint-device-DEBUG: 20:26:44.599: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s (process:4343): libfprint-device-DEBUG: 20:26:44.599: Not updating temperature model, device can run continuously! 196s enrolling 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 1, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 2, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 3, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 4, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 5, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 6, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 7, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 8, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 9, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 10, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 11, None, None, None) 196s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0x7c957d934180 (FpiDeviceGoodixMoc at 0x1a035070)>, 12, None, None, None) 196s enroll done 196s listing 196s listing done 196s verifying 196s verify done 196s async identifying 196s indentification_done: 196s deleting 196s delete done 196s ** (umockdev-run:4339): DEBUG: 20:26:44.612: umockdev.vala:154: Removing test bed /tmp/umockdev.K1P612 196s (umockdev-run:4339): GLib-DEBUG: 20:26:44.618: unsetenv() is not thread-safe and should not be used after threads are created 196s PASS: libfprint-2/driver-goodixmoc.test 196s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.1.test 196s TAP version 14 196s # random seed: R02S9e8076f5840d0636b4962dff77444a0a 196s 1..14 196s # Start of device tests 196s # Start of async tests 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.1 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.1 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 1 /device/async/open 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 2 /device/async/close 196s # End of async tests 196s # Start of sync tests 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 3 /device/sync/open 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 4 /device/sync/close 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 5 /device/sync/get_driver 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 6 /device/sync/get_device_id 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 7 /device/sync/get_name 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 8 /device/sync/get_scan_type 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 9 /device/sync/get_nr_enroll_stages 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 10 /device/sync/supports_identify 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 11 /device/sync/supports_capture 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 12 /device/sync/has_storage 196s # Start of open tests 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 13 /device/sync/open/notify 196s # End of open tests 196s # Start of close tests 196s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-ssm-test-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f6987, GType is 103486655645568 196s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.1 (Virtual device for SSM Testing) 196s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.1/libdevice-fake-tod-test-driver-v1+1.90.1-x86_64.so 196s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e642a3f053b, GType is 103486655650368 196s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.1 (Virtual device for debugging) 196s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 196s # libfprint-context-DEBUG: created 196s # libfprint-device-DEBUG: Device reported probe completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported open completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s # libfprint-device-DEBUG: Device reported close completion 196s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 196s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s ok 14 /device/sync/close/notify 196s # End of close tests 196s # End of sync tests 196s # End of device tests 196s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.1.test 196s Running test: libfprint-2/driver-elan-cobo.test 196s ** (umockdev-run:4383): DEBUG: 20:26:44.676: umockdev.vala:127: Created udev test bed /tmp/umockdev.5PNE22 196s ** (umockdev-run:4383): DEBUG: 20:26:44.676: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 196s ** (umockdev-run:4383): DEBUG: 20:26:44.677: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 196s ** (umockdev-run:4383): DEBUG: 20:26:44.680: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5PNE22/dev/bus/usb/001/045 196s ** (umockdev-run:4383): DEBUG: 20:26:44.680: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 196s ** (umockdev-run:4383): DEBUG: 20:26:44.681: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 196s ** (umockdev-run:4383): DEBUG: 20:26:44.684: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5PNE22/dev/bus/usb/001/001 196s ** (umockdev-run:4383): DEBUG: 20:26:44.684: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 196s ** (umockdev-run:4383): DEBUG: 20:26:44.684: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 196s (process:4387): libfprint-context-DEBUG: 20:26:44.757: Initializing FpContext (libfprint version 1.94.8+tod1) 196s (process:4387): libfprint-tod-DEBUG: 20:26:44.758: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 196s (process:4387): libfprint-context-DEBUG: 20:26:44.759: No driver found for USB device 1D6B:0002 196s (process:4387): libfprint-device-DEBUG: 20:26:44.760: Device reported probe completion 196s (process:4387): libfprint-device-DEBUG: 20:26:44.760: Completing action FPI_DEVICE_ACTION_PROBE in idle! 196s (process:4387): libfprint-device-DEBUG: 20:26:44.760: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164556605: ../libfprint/drivers/elan.c:908 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.761: Image device open completed 196s (process:4387): libfprint-device-DEBUG: 20:26:44.761: Device reported open completion 196s (process:4387): libfprint-device-DEBUG: 20:26:44.761: Completing action FPI_DEVICE_ACTION_OPEN in idle! 196s (process:4387): libfprint-device-DEBUG: 20:26:44.761: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:4387): libfprint-device-DEBUG: 20:26:44.761: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.761: Activating image device 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557041: ../libfprint/drivers/elan.c:960 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557045: ../libfprint/drivers/elan.c:951 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557047: ../libfprint/drivers/elan.c:892 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557050: ../libfprint/drivers/elan.c:100 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.761: [elan] ACTIVATE_NUM_STATES entering state 0 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557062: ../libfprint/drivers/elan.c:820 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557579: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557590: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.761: 164557593: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.762: 164558152: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.762: 164558165: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.762: [elan] ACTIVATE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.762: 164558173: ../libfprint/drivers/elan.c:820 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.762: FW ver 0x0140 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.762: [elan] ACTIVATE_NUM_STATES entering state 2 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.762: 164558180: ../libfprint/drivers/elan.c:820 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164558702: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164558713: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164558716: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559209: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559222: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.763: [elan] ACTIVATE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559228: ../libfprint/drivers/elan.c:820 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: sensor dimensions, WxH: 144x64 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.763: [elan] ACTIVATE_NUM_STATES entering state 4 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559235: ../libfprint/drivers/elan.c:820 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559241: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.763: [elan] ACTIVATE_NUM_STATES completed successfully 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559246: ../libfprint/drivers/elan.c:881 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.763: Image device activation completed 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559258: ../libfprint/drivers/elan.c:960 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559264: ../libfprint/drivers/elan.c:960 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559266: ../libfprint/drivers/elan.c:792 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559268: ../libfprint/drivers/elan.c:100 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.763: [elan] CALIBRATE_NUM_STATES entering state 0 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.763: 164559273: ../libfprint/drivers/elan.c:691 196s (process:4387): libfprint-device-DEBUG: 20:26:44.763: Device reported finger status change: FP_FINGER_STATUS_NEEDED 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164559658: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164559710: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164559737: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164560312: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164560388: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.764: [elan] CALIBRATE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164560424: ../libfprint/drivers/elan.c:691 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164560426: ../libfprint/drivers/elan.c:156 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164560431: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.764: [elan] CALIBRATE_NUM_STATES entering state 2 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.764: 164560446: ../libfprint/drivers/elan.c:691 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164560920: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164560974: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164560981: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164561397: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164561456: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.765: [elan] CALIBRATE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164561467: ../libfprint/drivers/elan.c:691 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164561469: ../libfprint/drivers/elan.c:634 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: calibration mean: 8248, bg mean: 7978, delta: 270 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.765: [elan] CALIBRATE_NUM_STATES completed successfully 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164561489: ../libfprint/drivers/elan.c:776 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164561492: ../libfprint/drivers/elan.c:620 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.765: 164561494: ../libfprint/drivers/elan.c:100 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.765: [elan] CAPTURE_NUM_STATES entering state 0 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: 164561916: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: 164561968: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: 164561986: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: skipping read, not expecting anything 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: 164562016: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.766: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: 164562440: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: 164562495: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.766: 164562548: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.767: 164562996: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.767: 164563073: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.767: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-device-DEBUG: 20:26:44.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.767: Image device reported finger status: on 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.767: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.767: 164563108: ../libfprint/drivers/elan.c:960 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.767: 164563484: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.767: 164563540: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.767: 164563548: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.768: 164563955: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.768: 164564030: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.768: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.768: 164564045: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.768: 164564052: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.768: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.768: 164564467: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.768: 164564519: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.768: 164564536: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.769: 164564926: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.769: 164564978: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.769: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.769: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.769: 164565360: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.769: 164565414: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.769: 164565430: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.770: 164565816: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.770: 164565838: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.770: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.770: 164565898: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.770: 164565904: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.770: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.770: 164566293: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.770: 164566353: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.770: 164566405: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.771: 164566846: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.771: 164566867: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.771: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.771: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.771: 164567314: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.771: 164567343: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.771: 164567355: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.772: 164567784: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.772: 164567794: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.772: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.772: 164567799: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.772: 164567805: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.772: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.772: 164568224: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.772: 164568251: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.772: 164568264: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164568658: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164568679: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.773: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.773: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164569043: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164569054: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164569057: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164569539: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164569549: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.773: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164569555: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.773: 164569561: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.773: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.774: 164569939: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.774: 164569966: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.774: 164569979: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.774: 164570447: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.774: 164570486: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.774: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.774: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.775: 164570971: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.775: 164570980: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.775: 164570983: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.775: 164571489: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.775: 164571503: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.775: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.775: 164571508: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.775: 164571515: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.775: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.776: 164571893: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.776: 164571916: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.776: 164571928: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.776: 164572351: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.776: 164572380: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.776: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.776: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.777: 164572761: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.777: 164572783: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.777: 164572787: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.777: 164573287: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.777: 164573314: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.777: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.777: 164573322: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.777: 164573328: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.777: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.778: 164573711: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.778: 164573733: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.778: 164573745: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.778: 164574166: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.778: 164574192: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.778: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.778: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164574628: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164574650: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164574654: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164575159: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164575172: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.779: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164575178: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164575184: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.779: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.779: 164575583: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.780: 164575637: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.780: 164575651: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.780: 164576035: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.780: 164576093: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.780: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.780: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.780: 164576454: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.780: 164576505: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.780: 164576521: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.781: 164576931: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.781: 164576984: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.781: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.781: 164577021: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.781: 164577028: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.781: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.781: 164577450: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.781: 164577503: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.781: 164577530: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.782: 164577887: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.782: 164577938: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.782: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.782: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.782: 164578319: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.782: 164578376: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.782: 164578391: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.783: 164578804: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.783: 164578827: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.783: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.783: 164578834: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.783: 164578844: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.783: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.783: 164579236: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.783: 164579290: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.783: 164579303: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.784: 164579664: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.784: 164579718: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.784: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.784: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.784: 164580111: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.784: 164580170: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.784: 164580186: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.784: 164580589: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164580639: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.785: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164580647: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164580661: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.785: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164581030: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164581091: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164581151: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164581543: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.785: 164581564: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.785: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.785: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.786: 164581958: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.786: 164581968: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.786: 164581970: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.786: 164582370: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.786: 164582398: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.786: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.786: 164582406: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.786: 164582412: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.786: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.787: 164582829: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.787: 164582881: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.787: 164582896: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.787: 164583271: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.787: 164583298: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.787: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.787: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164583652: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164583661: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164583664: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164584067: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164584100: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.788: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164584108: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164584114: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.788: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164584472: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164584482: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.788: 164584484: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.789: 164584870: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.789: 164584879: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.789: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.789: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.789: 164585237: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.789: 164585263: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.789: 164585268: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.790: 164585694: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.790: 164585750: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.790: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.790: 164585769: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.790: 164585777: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.790: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.790: 164586208: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.790: 164586268: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.790: 164586293: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.791: 164586682: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.791: 164586733: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.791: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.791: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.791: 164587108: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.791: 164587171: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.791: 164587179: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.791: 164587600: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164587610: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.792: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164587616: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164587622: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.792: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164588026: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164588087: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164588102: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164588477: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.792: 164588524: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.792: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.792: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.793: 164588894: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.793: 164588947: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.793: 164588963: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.793: 164589360: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.793: 164589439: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.793: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.793: 164589450: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.793: 164589457: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.793: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.794: 164589883: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.794: 164589945: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.794: 164589961: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.794: 164590327: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.794: 164590390: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.794: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-image_device-DEBUG: 20:26:44.794: Image device reported finger status: on 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.795: 164590825: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.795: 164590877: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.795: 164590884: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.795: 164591305: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.795: 164591332: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.795: [elan] CAPTURE_NUM_STATES entering state 3 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.795: 164591340: ../libfprint/drivers/elan.c:203 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.795: 164591347: ../libfprint/drivers/elan.c:118 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.795: [elan] CAPTURE_NUM_STATES entering state 1 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164591702: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164591757: ../libfprint/drivers/elan.c:366 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164591773: ../libfprint/drivers/elan.c:379 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164592131: ../libfprint/drivers/elan.c:346 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164592159: ../libfprint/drivers/elan.c:335 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.796: [elan] CAPTURE_NUM_STATES entering state 2 196s (process:4387): libfprint-SSM-DEBUG: 20:26:44.796: [elan] CAPTURE_NUM_STATES completed successfully 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164592224: ../libfprint/drivers/elan.c:586 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164592227: ../libfprint/drivers/elan.c:315 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.796: 164592233: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.797: 164592946: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.798: 164593645: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.798: 164594405: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.799: 164595172: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.800: 164595915: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.801: 164596659: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.801: 164597429: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.802: 164598187: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.803: 164598927: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.804: 164599669: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.804: 164600406: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.805: 164601149: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-elan-DEBUG: 20:26:44.806: 164601883: ../libfprint/drivers/elan.c:272 196s (process:4387): libfprint-assembling-DEBUG: 20:26:44.916: calc delta completed in 0.109628 secs 197s (process:4387): libfprint-assembling-DEBUG: 20:26:45.059: calc delta completed in 0.142817 secs 197s (process:4387): libfprint-assembling-DEBUG: 20:26:45.059: errors: 133465 rev: 143589 197s (process:4387): libfprint-assembling-DEBUG: 20:26:45.166: calc delta completed in 0.106523 secs 197s (process:4387): libfprint-assembling-DEBUG: 20:26:45.166: height is 225 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.166: Image device captured an image 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.167: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.167: 164962782: ../libfprint/drivers/elan.c:960 197s (process:4387): libfprint-device-DEBUG: 20:26:45.167: Device reported finger status change: FP_FINGER_STATUS_PRESENT 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.167: 164962890: ../libfprint/drivers/elan.c:507 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.167: 164962941: ../libfprint/drivers/elan.c:100 197s (process:4387): libfprint-SSM-DEBUG: 20:26:45.167: [elan] STOP_CAPTURE_NUM_STATES entering state 0 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.167: 164963077: ../libfprint/drivers/elan.c:466 197s (process:4387): libfprint-device-DEBUG: 20:26:45.167: Updated temperature model after 0.41 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.167: 164963522: ../libfprint/drivers/elan.c:346 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164963593: ../libfprint/drivers/elan.c:366 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164963656: ../libfprint/drivers/elan.c:379 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: skipping read, not expecting anything 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164963790: ../libfprint/drivers/elan.c:335 197s (process:4387): libfprint-SSM-DEBUG: 20:26:45.168: [elan] STOP_CAPTURE_NUM_STATES completed successfully 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164963923: ../libfprint/drivers/elan.c:483 197s (process:4387): libfprint-device-DEBUG: 20:26:45.168: Device reported finger status change: FP_FINGER_STATUS_NONE 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.168: Image device reported finger status: off 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164964149: ../libfprint/drivers/elan.c:960 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.168: Deactivating image device 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164964159: ../libfprint/drivers/elan.c:960 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164964162: ../libfprint/drivers/elan.c:975 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.168: Image device deactivation completed 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.168: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.168: 164964173: ../libfprint/drivers/elan.c:960 197s (process:4387): libfprint-image-DEBUG: 20:26:45.179: Minutiae scan completed in 0.011999 secs 197s (process:4387): libfprint-device-DEBUG: 20:26:45.179: Device reported capture completion 197s (process:4387): libfprint-device-DEBUG: 20:26:45.179: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 197s (process:4387): libfprint-device-DEBUG: 20:26:45.179: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.179: 164975070: ../libfprint/drivers/elan.c:939 197s (process:4387): libfprint-elan-DEBUG: 20:26:45.179: 164975080: ../libfprint/drivers/elan.c:100 197s (process:4387): libfprint-image_device-DEBUG: 20:26:45.179: Image device close completed 197s (process:4387): libfprint-device-DEBUG: 20:26:45.179: Device reported close completion 197s (process:4387): libfprint-device-DEBUG: 20:26:45.179: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 197s (process:4387): libfprint-device-DEBUG: 20:26:45.179: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 197s ** (umockdev-run:4383): DEBUG: 20:26:45.252: umockdev.vala:154: Removing test bed /tmp/umockdev.5PNE22 197s (umockdev-run:4383): GLib-DEBUG: 20:26:45.257: unsetenv() is not thread-safe and should not be used after threads are created 197s Comparing PNGs /tmp/libfprint-umockdev-test-x6n1f6qe/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 197s PASS: libfprint-2/driver-elan-cobo.test 197s Running test: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.94.7.test 197s TAP version 14 197s # random seed: R02Se587f5f11270d7c99097259dac3efbbc 197s 1..4 197s # Start of context tests 197s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 197s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 197s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7624d75719d3, GType is 95594809212304 197s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 197s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 197s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7624d756bb7b, GType is 95594809216976 197s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 197s ok 1 /context/new 197s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 197s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 197s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 197s ok 2 /context/no-devices 197s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 197s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 197s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7624d75719d3, GType is 95594809212304 197s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 197s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 197s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7624d756bb7b, GType is 95594809216976 197s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 197s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 197s # libfprint-context-DEBUG: created 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM_SINGLE_STATE entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM_SINGLE_STATE completed successfully 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 14 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state -10 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 197s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 14 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state -10 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: non-cleanup 198s # libfprint-device-DEBUG: Device reported probe completion 198s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 198s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 198s ok 3 /context/has-virtual-device 198s # slow test /context/has-virtual-device executed in 1.04 secs 198s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 198s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-ssm-test-v1+1.94.7-x86_64.so 198s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7624d75719d3, GType is 95594809212304 198s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.94.7 (Virtual device for SSM Testing) 198s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.94.7/libdevice-fake-tod-test-driver-v1+1.94.7-x86_64.so 198s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7624d756bb7b, GType is 95594809216976 198s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.94.7 (Virtual device for debugging) 198s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 198s # libfprint-context-DEBUG: created 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM_SINGLE_STATE entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM_SINGLE_STATE completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 14 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state -10 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 198s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 14 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state -10 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 199s Executing: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.94.7.test 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM cancelled delayed state change 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 1 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed successfully 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed successfully 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed successfully 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 1 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later. 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later. 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed successfully 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 0 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 2 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM entering state 3 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 199s # libfprint-SSM-DEBUG: [ssm_test_dev_tod_v1+1.94.7] FPI_TEST_SSM completed with error: non-cleanup 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 1.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 4 /context/enumerates-new-devices 199s # slow test /context/enumerates-new-devices executed in 1.04 secs 199s # End of context tests 199s PASS: libfprint-2/tod-fp-context-tod-ssm_test_dev_tod_v1+1.94.7.test 199s Running test: libfprint-2/driver-uru4000-msv2.test 199s ** (umockdev-run:4408): DEBUG: 20:26:47.395: umockdev.vala:127: Created udev test bed /tmp/umockdev.Z2H912 199s ** (umockdev-run:4408): DEBUG: 20:26:47.395: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 199s ** (umockdev-run:4408): DEBUG: 20:26:47.396: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 199s ** (umockdev-run:4408): DEBUG: 20:26:47.399: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z2H912/dev/bus/usb/001/047 199s ** (umockdev-run:4408): DEBUG: 20:26:47.399: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 199s ** (umockdev-run:4408): DEBUG: 20:26:47.400: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 199s ** (umockdev-run:4408): DEBUG: 20:26:47.402: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z2H912/dev/bus/usb/001/001 199s ** (umockdev-run:4408): DEBUG: 20:26:47.402: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 199s ** (umockdev-run:4408): DEBUG: 20:26:47.403: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 199s (process:4412): libfprint-context-DEBUG: 20:26:47.477: Initializing FpContext (libfprint version 1.94.8+tod1) 199s (process:4412): libfprint-tod-DEBUG: 20:26:47.477: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 199s (process:4412): libfprint-context-DEBUG: 20:26:47.479: No driver found for USB device 1D6B:0002 199s (process:4412): libfprint-device-DEBUG: 20:26:47.479: Device reported probe completion 199s (process:4412): libfprint-device-DEBUG: 20:26:47.479: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s (process:4412): libfprint-device-DEBUG: 20:26:47.479: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:4412): GLib-DEBUG: 20:26:47.481: setenv()/putenv() are not thread-safe and should not be used after threads are created 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.482: Image device open completed 199s (process:4412): libfprint-device-DEBUG: 20:26:47.482: Device reported open completion 199s (process:4412): libfprint-device-DEBUG: 20:26:47.482: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:4412): libfprint-device-DEBUG: 20:26:47.483: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:4412): libfprint-device-DEBUG: 20:26:47.483: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.483: Activating image device 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.483: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.483: [uru4000] INIT_NUM_STATES entering state 0 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.483: read 1 regs at 7 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.484: reg value 3 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.484: [uru4000] INIT_NUM_STATES entering state 1 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.484: [uru4000] INIT_NUM_STATES entering state 3 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.484: set 83 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.485: [uru4000] INIT_NUM_STATES entering state 4 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.485: [uru4000] POWERUP_NUM_STATES entering state 0 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.485: [uru4000] POWERUP_NUM_STATES entering state 1 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.485: set 03 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.485: [uru4000] POWERUP_NUM_STATES entering state 2 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.485: read 1 regs at 7 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.486: reg value 83 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.486: [uru4000] POWERUP_NUM_STATES entering state 3 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.486: [uru4000] POWERUP_NUM_STATES entering state 4 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.496: [uru4000] POWERUP_NUM_STATES entering state 5 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.496: 167291910: ../libfprint/drivers/uru4000.c:291 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.497: [uru4000] POWERUP_NUM_STATES entering state 6 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.497: [uru4000] POWERUP_NUM_STATES entering state 1 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.497: set 03 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.497: [uru4000] POWERUP_NUM_STATES entering state 2 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.498: read 1 regs at 7 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.498: reg value 3 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.498: [uru4000] POWERUP_NUM_STATES entering state 3 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.498: [uru4000] POWERUP_NUM_STATES completed successfully 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.498: [uru4000] INIT_NUM_STATES entering state 5 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.499: recv irq type 56aa 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.499: late scanpwr interrupt 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.499: [uru4000] INIT_NUM_STATES entering state 6 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.499: [uru4000] INIT_NUM_STATES entering state 7 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.499: read 16 regs at f0 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.499: reg value 50 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.499: [uru4000] INIT_NUM_STATES entering state 8 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.499: Versions 0059 and 0034 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.499: [uru4000] INIT_NUM_STATES completed successfully 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.499: Image device activation completed 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.499: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.499: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.499: wait finger on 199s (process:4412): libfprint-device-DEBUG: 20:26:47.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.500: recv irq type 0101 199s (process:4412): libfprint-device-DEBUG: 20:26:47.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.500: Image device reported finger status: on 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.500: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.500: starting capture 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.500: Image encryption seed: 1374298404 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.500: [uru4000] IMAGING_NUM_STATES entering state 0 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.502: [uru4000] IMAGING_NUM_STATES entering state 1 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.502: hw header lines 289 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.502: dev2: 10849 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.502: image seems to be encrypted 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.502: [uru4000] IMAGING_NUM_STATES entering state 2 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.502: read 4 regs at 34 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: reg value 7b 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.503: [uru4000] IMAGING_NUM_STATES entering state 3 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: encryption id 05 -> key db896f5f 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 0 02 67 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: decoding 67 lines 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 1 00 1 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: skipping 1 lines 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 2 02 49 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: decoding 49 lines 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 3 01 1 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: skipping 1 lines 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 4 00 1 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: skipping 1 lines 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 5 02 49 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: decoding 49 lines 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 6 00 1 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: skipping 1 lines 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: 7 02 121 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.503: decoding 121 lines 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.504: [uru4000] IMAGING_NUM_STATES entering state 4 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.504: Image device captured an image 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.504: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 199s (process:4412): libfprint-device-DEBUG: 20:26:47.504: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4412): libfprint-SSM-DEBUG: 20:26:47.504: [uru4000] IMAGING_NUM_STATES completed successfully 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.504: await finger off 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.506: recv irq type 0200 199s (process:4412): libfprint-device-DEBUG: 20:26:47.506: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.506: Image device reported finger status: off 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.506: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.506: Deactivating image device 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.506: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.506: deactivating 199s (process:4412): libfprint-uru4000-DEBUG: 20:26:47.508: cancelled 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.508: Image device deactivation completed 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.508: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 199s (process:4412): libfprint-image-DEBUG: 20:26:47.545: Minutiae scan completed in 0.041449 secs 199s (process:4412): libfprint-device-DEBUG: 20:26:47.546: Device reported capture completion 199s (process:4412): libfprint-device-DEBUG: 20:26:47.546: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 199s (process:4412): libfprint-device-DEBUG: 20:26:47.546: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 199s (process:4412): libfprint-image_device-DEBUG: 20:26:47.547: Image device close completed 199s (process:4412): libfprint-device-DEBUG: 20:26:47.547: Device reported close completion 199s (process:4412): libfprint-device-DEBUG: 20:26:47.547: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s (process:4412): libfprint-device-DEBUG: 20:26:47.547: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 199s ** (umockdev-run:4408): DEBUG: 20:26:47.677: umockdev.vala:154: Removing test bed /tmp/umockdev.Z2H912 199s (umockdev-run:4408): GLib-DEBUG: 20:26:47.683: unsetenv() is not thread-safe and should not be used after threads are created 199s Comparing PNGs /tmp/libfprint-umockdev-test-dl0lb9ay/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 199s PASS: libfprint-2/driver-uru4000-msv2.test 199s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 199s TAP version 14 199s # random seed: R02S7d2c321b142ea410dacaae51a077760e 199s 1..14 199s # Start of device tests 199s # Start of async tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 1 /device/async/open 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 2 /device/async/close 199s # End of async tests 199s # Start of sync tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 3 /device/sync/open 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 4 /device/sync/close 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 5 /device/sync/get_driver 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 6 /device/sync/get_device_id 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 7 /device/sync/get_name 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 8 /device/sync/get_scan_type 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 9 /device/sync/get_nr_enroll_stages 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 10 /device/sync/supports_identify 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 11 /device/sync/supports_capture 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 12 /device/sync/has_storage 199s # Start of open tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 13 /device/sync/open/notify 199s # End of open tests 199s # Start of close tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7b4c79c454b0, GType is 98573376952048 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 199s # 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 199s # 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 199s # 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 14 /device/sync/close/notify 199s # End of close tests 199s # End of sync tests 199s # End of device tests 199s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 199s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.2.test 199s TAP version 14 199s # random seed: R02S3b4bc5248fe7e8a59830922161350695 199s 1..14 199s # Start of device tests 199s # Start of async tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.2 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.2 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 1 /device/async/open 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 2 /device/async/close 199s # End of async tests 199s # Start of sync tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 3 /device/sync/open 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 4 /device/sync/close 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 5 /device/sync/get_driver 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 6 /device/sync/get_device_id 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 7 /device/sync/get_name 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 8 /device/sync/get_scan_type 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 9 /device/sync/get_nr_enroll_stages 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 10 /device/sync/supports_identify 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 11 /device/sync/supports_capture 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 12 /device/sync/has_storage 199s # Start of open tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 13 /device/sync/open/notify 199s # End of open tests 199s # Start of close tests 199s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-ssm-test-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bade987, GType is 110357488867200 199s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.2 (Virtual device for SSM Testing) 199s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.2/libdevice-fake-tod-test-driver-v1+1.90.2-x86_64.so 199s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7e543bad853b, GType is 110357488872000 199s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.2 (Virtual device for debugging) 199s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 199s # libfprint-context-DEBUG: created 199s # libfprint-device-DEBUG: Device reported probe completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported open completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s # libfprint-device-DEBUG: Device reported close completion 199s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 199s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 199s ok 14 /device/sync/close/notify 199s # End of close tests 199s # End of sync tests 199s # End of device tests 199s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_v1+1.90.2.test 199s Running test: libfprint-2/driver-realtek.test 199s ** (umockdev-run:4485): DEBUG: 20:26:47.789: umockdev.vala:127: Created udev test bed /tmp/umockdev.WGVH22 199s ** (umockdev-run:4485): DEBUG: 20:26:47.790: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8 199s ** (umockdev-run:4485): DEBUG: 20:26:47.792: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb) 199s ** (umockdev-run:4485): DEBUG: 20:26:47.796: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WGVH22/dev/bus/usb/001/025 199s ** (umockdev-run:4485): DEBUG: 20:26:47.796: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 199s ** (umockdev-run:4485): DEBUG: 20:26:47.797: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 199s ** (umockdev-run:4485): DEBUG: 20:26:47.800: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WGVH22/dev/bus/usb/001/001 199s ** (umockdev-run:4485): DEBUG: 20:26:47.800: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 199s ** (umockdev-run:4485): DEBUG: 20:26:47.800: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 199s (process:4489): libfprint-context-DEBUG: 20:26:47.873: Initializing FpContext (libfprint version 1.94.8+tod1) 199s (process:4489): libfprint-tod-DEBUG: 20:26:47.873: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 199s (process:4489): libfprint-context-DEBUG: 20:26:47.875: No driver found for USB device 1D6B:0002 199s (process:4489): libfprint-realtek-DEBUG: 20:26:47.875: 167671356: ../libfprint/drivers/realtek/realtek.c:1225 199s (process:4489): libfprint-realtek-DEBUG: 20:26:47.877: Device name: Realtek USB2.0 Finger Print Bridge 199s (process:4489): libfprint-device-DEBUG: 20:26:47.878: Device reported probe completion 199s (process:4489): libfprint-device-DEBUG: 20:26:47.878: Completing action FPI_DEVICE_ACTION_PROBE in idle! 199s (process:4489): libfprint-device-DEBUG: 20:26:47.878: Not updating temperature model, device can run continuously! 199s (process:4489): libfprint-realtek-DEBUG: 20:26:47.878: 167674515: ../libfprint/drivers/realtek/realtek.c:1270 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.879: [realtek] Init entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.879: [realtek] Init entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.879: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.880: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.880: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.880: [realtek] Init entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.880: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.881: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.881: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.881: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.882: [realtek] Init completed successfully 199s (process:4489): libfprint-realtek-DEBUG: 20:26:47.882: Init complete! 199s (process:4489): libfprint-device-DEBUG: 20:26:47.882: Device reported open completion 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.882: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-device-DEBUG: 20:26:47.882: Completing action FPI_DEVICE_ACTION_OPEN in idle! 199s (process:4489): libfprint-device-DEBUG: 20:26:47.882: Not updating temperature model, device can run continuously! 199s (process:4489): libfprint-realtek-DEBUG: 20:26:47.882: 167677870: ../libfprint/drivers/realtek/realtek.c:1333 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.882: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-realtek-DEBUG: 20:26:47.883: Successfully cleared storage 199s (process:4489): libfprint-device-DEBUG: 20:26:47.883: Device reported deletion completion 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.883: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-device-DEBUG: 20:26:47.883: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 199s (process:4489): libfprint-device-DEBUG: 20:26:47.883: Not updating temperature model, device can run continuously! 199s (process:4489): libfprint-device-DEBUG: 20:26:47.883: Not updating temperature model, device can run continuously! 199s (process:4489): libfprint-realtek-DEBUG: 20:26:47.883: 167679300: ../libfprint/drivers/realtek/realtek.c:1202 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.883: [realtek] Enroll entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.883: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.884: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.884: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.885: [realtek] Enroll entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.885: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.885: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.885: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.885: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.885: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.885: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.886: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.886: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.886: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.886: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.886: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.887: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.887: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.887: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.888: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.888: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.888: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.888: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.888: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.889: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.889: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.889: Device reported enroll progress, reported 1 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.889: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.889: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.889: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.890: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.890: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.890: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.890: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.890: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.891: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.891: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.891: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.892: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.892: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.892: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.892: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.892: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.893: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.893: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.893: Device reported enroll progress, reported 2 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.893: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.893: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.893: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.893: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.893: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.894: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.894: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.894: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.894: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.895: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.895: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.896: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.896: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.896: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.896: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.897: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.897: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.897: Device reported enroll progress, reported 3 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.897: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.897: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.897: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.898: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.898: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.898: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.898: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.899: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.899: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.899: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.900: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.900: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.900: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.900: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.900: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.901: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.902: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.902: Device reported enroll progress, reported 4 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.902: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.902: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.902: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.902: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.902: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.903: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.903: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.903: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.904: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.904: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.905: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.905: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.905: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.905: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.905: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.906: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.907: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.907: Device reported enroll progress, reported 5 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.907: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.907: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.907: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.907: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.908: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.908: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.908: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.908: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.909: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.910: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.910: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.910: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.910: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.911: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.911: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.911: Device reported enroll progress, reported 6 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.911: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.911: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.912: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.912: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.912: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.912: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.912: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.913: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.913: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.913: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.914: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.914: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.914: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.914: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.915: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.916: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.916: Device reported enroll progress, reported 7 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.916: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.916: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.916: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.916: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.917: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.917: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.917: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.917: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.917: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.918: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.918: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.919: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.919: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.919: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.919: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.919: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.920: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.921: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-device-DEBUG: 20:26:47.921: Device reported enroll progress, reported 8 of 8 have been completed 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.921: [realtek] Enroll entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.921: Device reported finger status change: FP_FINGER_STATUS_NEEDED 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.921: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.921: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.921: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.921: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.922: [realtek] Enroll entering state 3 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.922: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.922: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.922: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.923: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.924: Device reported finger status change: FP_FINGER_STATUS_PRESENT 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.924: [realtek] Enroll entering state 4 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.924: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.924: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.924: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.925: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 199s (process:4489): libfprint-device-DEBUG: 20:26:47.925: Device reported finger status change: FP_FINGER_STATUS_NONE 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.925: [realtek] Enroll entering state 5 199s (process:4489): libfprint-SSM-DEBUG: 20:26:47.925: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.926: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.926: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.927: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.927: [realtek] Enroll entering state 6 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.927: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.927: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.928: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.928: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.928: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.929: [realtek] Enroll completed successfully 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.929: Enrollment complete! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.929: Device reported enroll completion 200s (process:4489): libfprint-device-DEBUG: 20:26:47.929: Print for finger FP_FINGER_UNKNOWN enrolled 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.929: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-device-DEBUG: 20:26:47.929: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.929: Not updating temperature model, device can run continuously! 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.929: 167725291: ../libfprint/drivers/realtek/realtek.c:1345 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.929: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.930: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.930: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.931: Query templates complete! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.931: Device reported listing completion 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.931: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-device-DEBUG: 20:26:47.931: Completing action FPI_DEVICE_ACTION_LIST in idle! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.931: Not updating temperature model, device can run continuously! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.931: Not updating temperature model, device can run continuously! 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.931: 167727236: ../libfprint/drivers/realtek/realtek.c:1178 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.931: [realtek] Verify & Identify entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.931: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.932: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.932: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.933: [realtek] Verify & Identify entering state 1 200s (process:4489): libfprint-device-DEBUG: 20:26:47.933: Device reported finger status change: FP_FINGER_STATUS_NEEDED 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.933: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.933: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.933: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.933: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.934: [realtek] Verify & Identify entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.934: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.934: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.934: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.935: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-device-DEBUG: 20:26:47.936: Device reported finger status change: FP_FINGER_STATUS_PRESENT 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.936: [realtek] Verify & Identify entering state 3 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.936: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.936: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.936: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.937: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-device-DEBUG: 20:26:47.937: Device reported finger status change: FP_FINGER_STATUS_NONE 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.938: [realtek] Verify & Identify entering state 4 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.938: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.938: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.938: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.939: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-device-DEBUG: 20:26:47.939: Device reported verify result 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.939: [realtek] Verify & Identify entering state 5 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.939: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.940: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.940: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.940: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.940: [realtek] Verify & Identify completed successfully 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.940: Verify complete! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.940: Device reported verify completion 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.940: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-device-DEBUG: 20:26:47.940: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.940: Not updating temperature model, device can run continuously! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.941: Not updating temperature model, device can run continuously! 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.941: 167736837: ../libfprint/drivers/realtek/realtek.c:1178 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.941: [realtek] Verify & Identify entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.941: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.941: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.942: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.943: [realtek] Verify & Identify entering state 1 200s (process:4489): libfprint-device-DEBUG: 20:26:47.943: Device reported finger status change: FP_FINGER_STATUS_NEEDED 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.943: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.943: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.943: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.943: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.944: [realtek] Verify & Identify entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.944: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.944: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.945: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.945: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-device-DEBUG: 20:26:47.946: Device reported finger status change: FP_FINGER_STATUS_PRESENT 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.946: [realtek] Verify & Identify entering state 3 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.946: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.946: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.946: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.947: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-device-DEBUG: 20:26:47.948: Device reported finger status change: FP_FINGER_STATUS_NONE 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.948: [realtek] Verify & Identify entering state 4 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.948: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.948: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.948: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.949: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-device-DEBUG: 20:26:47.950: Device reported identify result 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.950: [realtek] Verify & Identify completed successfully 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.950: Verify complete! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.950: Device reported identify completion 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.950: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-device-DEBUG: 20:26:47.950: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.950: Not updating temperature model, device can run continuously! 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.950: 167746116: ../libfprint/drivers/realtek/realtek.c:1314 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.950: [realtek] Delete print entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.950: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.951: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.951: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.952: [realtek] Delete print entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.952: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.952: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.953: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.953: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.953: [realtek] Delete print completed successfully 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.953: Delete print complete! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.953: Device reported deletion completion 200s (process:4489): libfprint-SSM-DEBUG: 20:26:47.953: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 200s (process:4489): libfprint-device-DEBUG: 20:26:47.953: Completing action FPI_DEVICE_ACTION_DELETE in idle! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.953: Not updating temperature model, device can run continuously! 200s (process:4489): libfprint-realtek-DEBUG: 20:26:47.953: 167749394: ../libfprint/drivers/realtek/realtek.c:1302 200s (process:4489): libfprint-device-DEBUG: 20:26:47.953: Device reported close completion 200s (process:4489): libfprint-device-DEBUG: 20:26:47.954: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4489): libfprint-device-DEBUG: 20:26:47.954: Not updating temperature model, device can run continuously! 200s enrolling 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 1, None, None, None) 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 2, None, None, None) 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 3, None, None, None) 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 4, None, None, None) 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 5, None, None, None) 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 6, None, None, None) 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 7, None, None, None) 200s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x79f3cb872240 (FpiDeviceRealtek at 0x2b4ae180)>, 8, None, None, None) 200s enroll done 200s listing 200s listing done 200s verifying 200s verify done 200s async identifying 200s indentification_done: 200s deleting 200s delete done 200s ** (umockdev-run:4485): DEBUG: 20:26:47.966: umockdev.vala:154: Removing test bed /tmp/umockdev.WGVH22 200s (umockdev-run:4485): GLib-DEBUG: 20:26:47.972: unsetenv() is not thread-safe and should not be used after threads are created 200s PASS: libfprint-2/driver-realtek.test 200s Running test: libfprint-2/virtual-device.test 200s (process:4495): libfprint-context-DEBUG: 20:26:48.098: Initializing FpContext (libfprint version 1.94.8+tod1) 200s (process:4495): libfprint-tod-DEBUG: 20:26:48.098: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 200s (process:4495): libfprint-context-DEBUG: 20:26:48.099: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-cvf_b2gn/virtual-device.socket 200s (process:4495): libfprint-context-DEBUG: 20:26:48.099: created 200s (process:4495): libfprint-device-DEBUG: 20:26:48.099: Device reported probe completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.099: Completing action FPI_DEVICE_ACTION_PROBE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.099: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.100: 167895892: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.100: 167895993: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:4495): libfprint-device-DEBUG: 20:26:48.100: Device reported open completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.100: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.100: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.101: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.101: Got instructions of length 16 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.101: Received command SET_KEEP_ALIVE 0 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.101: Keep alive toggled: 0 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.101: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.101: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.101: Received command SET_ENROLL_STAGES 5 200s (process:4495): libfprint-device-DEBUG: 20:26:48.101: Device reported close completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.101: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.101: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.102: 167897621: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.102: 167897634: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:4495): libfprint-device-DEBUG: 20:26:48.102: Device reported open completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.102: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.102: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.102: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.102: Got instructions of length 20 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.102: Received command SET_ENROLL_STAGES 20 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.102: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.102: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.102: Received command SET_ENROLL_STAGES 1 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.103: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.103: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.103: Received command SET_ENROLL_STAGES 0 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.105: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.105: Got instructions of length 16 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.105: Received command SET_KEEP_ALIVE 0 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.105: Keep alive toggled: 0 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.105: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.105: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.105: Received command SET_ENROLL_STAGES 5 200s (process:4495): libfprint-device-DEBUG: 20:26:48.105: Device reported close completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.105: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.105: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.106: 167901769: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.106: 167901781: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:4495): libfprint-device-DEBUG: 20:26:48.106: Device reported open completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.106: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.106: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.106: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.106: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.106: Received command SET_SCAN_TYPE press 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.106: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.106: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.106: Received command SET_SCAN_TYPE swipe 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.107: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Got instructions of length 25 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Received command SET_SCAN_TYPE eye-contact 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.107: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Got instructions of length 16 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Received command SET_KEEP_ALIVE 0 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Keep alive toggled: 0 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.107: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Received command SET_ENROLL_STAGES 5 200s (process:4495): libfprint-device-DEBUG: 20:26:48.107: Device reported close completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.107: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.107: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: 167903213: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.107: 167903219: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:4495): libfprint-device-DEBUG: 20:26:48.107: Device reported open completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.107: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.107: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.107: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Got instructions of length 9 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Received command SLEEP 100 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.107: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Got instructions of length 7 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.107: Received command ERROR 4 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.108: Processing command SLEEP 100 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.108: Sleeping 100ms 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.208: Sleeping completed 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.208: Processing command ERROR 4 200s (process:4495): libfprint-device-DEBUG: 20:26:48.208: Device reported close completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.208: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.208: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: 168004694: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-device-DEBUG: 20:26:48.209: Device reported open completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.209: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.209: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.209: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: Got instructions of length 16 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: Received command SET_KEEP_ALIVE 1 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: Keep alive toggled: 1 200s (process:4495): libfprint-device-DEBUG: 20:26:48.209: Device reported close completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.209: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.209: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.209: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: Got instructions of length 9 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: Received command SLEEP 500 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: 168005255: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: Processing command SLEEP 500 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.209: Sleeping 500ms 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.710: Sleeping completed 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.710: 168505913: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-device-DEBUG: 20:26:48.710: Device reported open completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.710: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.710: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.710: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.710: Got instructions of length 16 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.710: Received command SET_KEEP_ALIVE 0 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.710: Keep alive toggled: 0 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.710: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.710: Got instructions of length 19 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.710: Received command SET_ENROLL_STAGES 5 200s (process:4495): libfprint-device-DEBUG: 20:26:48.710: Device reported close completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.710: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.710: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s ok 200s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: 168506681: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.711: 168506694: ../libfprint/drivers/virtual-device-listener.c:153 200s (process:4495): libfprint-device-DEBUG: 20:26:48.711: Device reported open completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.711: Completing action FPI_DEVICE_ACTION_OPEN in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.711: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.711: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: Got instructions of length 16 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: Received command IGNORED_COMMAND 200s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:48.711: Got a new connection! 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: Got instructions of length 9 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: Received command SLEEP 500 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: Processing command IGNORED_COMMAND 200s (process:4495): libfprint-device-DEBUG: 20:26:48.711: Device reported close completion 200s (process:4495): libfprint-device-DEBUG: 20:26:48.711: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 200s (process:4495): libfprint-device-DEBUG: 20:26:48.711: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: 168507358: ../libfprint/drivers/virtual-device.c:387 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: Processing command SLEEP 500 200s (process:4495): libfprint-virtual_device-DEBUG: 20:26:48.711: Sleeping 500ms 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.212: Sleeping completed 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.212: 169007977: ../libfprint/drivers/virtual-device.c:387 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.212: 169007999: ../libfprint/drivers/virtual-device-listener.c:153 201s (process:4495): libfprint-device-DEBUG: 20:26:49.212: Device reported open completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.212: Completing action FPI_DEVICE_ACTION_OPEN in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.212: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.212: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.212: Got instructions of length 16 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.212: Received command SET_KEEP_ALIVE 0 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.212: Keep alive toggled: 0 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.213: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: Got instructions of length 19 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: Received command SET_ENROLL_STAGES 5 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Device reported close completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s ok 201s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: 169009086: ../libfprint/drivers/virtual-device.c:387 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.213: 169009097: ../libfprint/drivers/virtual-device-listener.c:153 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Device reported open completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Completing action FPI_DEVICE_ACTION_OPEN in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.213: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: Got instructions of length 16 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: Received command SET_KEEP_ALIVE 1 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: Keep alive toggled: 1 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Device reported close completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.213: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.213: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: Got instructions of length 9 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.213: Received command SLEEP 500 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.214: 169009628: ../libfprint/drivers/virtual-device.c:387 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.214: Processing command SLEEP 500 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.214: Sleeping 500ms 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.714: Sleeping completed 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.714: 169510296: ../libfprint/drivers/virtual-device.c:387 201s (process:4495): libfprint-device-DEBUG: 20:26:49.714: Device reported open completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.714: Completing action FPI_DEVICE_ACTION_OPEN in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.714: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.715: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Got instructions of length 16 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Received command SET_KEEP_ALIVE 0 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Keep alive toggled: 0 201s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 201s self.assertFalse(self.dev.supports_identify()) 201s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 201s self.assertFalse(self.dev.supports_capture()) 201s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 201s self.assertFalse(self.dev.has_storage()) 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.715: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Got instructions of length 19 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Received command SET_ENROLL_STAGES 5 201s (process:4495): libfprint-device-DEBUG: 20:26:49.715: Device reported close completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.715: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.715: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s ok 201s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: 169511172: ../libfprint/drivers/virtual-device.c:387 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.715: 169511184: ../libfprint/drivers/virtual-device-listener.c:153 201s (process:4495): libfprint-device-DEBUG: 20:26:49.715: Device reported open completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.715: Completing action FPI_DEVICE_ACTION_OPEN in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.715: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.715: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Got instructions of length 16 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Received command SET_KEEP_ALIVE 0 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.715: Keep alive toggled: 0 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.716: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: Got instructions of length 19 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: Received command SET_ENROLL_STAGES 5 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Device reported close completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s ok 201s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: 169511852: ../libfprint/drivers/virtual-device.c:387 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.716: 169511860: ../libfprint/drivers/virtual-device-listener.c:153 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Device reported open completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Completing action FPI_DEVICE_ACTION_OPEN in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.716: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: Got instructions of length 16 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: Received command SET_KEEP_ALIVE 0 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: Keep alive toggled: 0 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.716: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: Got instructions of length 19 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: Received command SET_ENROLL_STAGES 5 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Device reported close completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.716: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s ok 201s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.716: 169512552: ../libfprint/drivers/virtual-device.c:387 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.716: 169512562: ../libfprint/drivers/virtual-device-listener.c:153 201s (process:4495): libfprint-device-DEBUG: 20:26:49.717: Device reported open completion 201s (process:4495): libfprint-device-DEBUG: 20:26:49.717: Completing action FPI_DEVICE_ACTION_OPEN in idle! 201s (process:4495): libfprint-device-DEBUG: 20:26:49.717: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:49.717: Got a new connection! 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.717: Got instructions of length 10 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.717: Received command SLEEP 1500 201s (process:4495): libfprint-device-DEBUG: 20:26:49.717: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.717: Processing command SLEEP 1500 201s (process:4495): libfprint-virtual_device-DEBUG: 20:26:49.717: Sleeping 1500ms 202s (process:4495): libfprint-device-DEBUG: 20:26:50.015: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 202s (process:4495): libfprint-device-DEBUG: 20:26:50.017: Idle cancelling on ongoing operation! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.017: Got cancellation! 202s (process:4495): libfprint-device-DEBUG: 20:26:50.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.017: Virtual device scan failed with error: Operation was cancelled 202s (process:4495): libfprint-device-DEBUG: 20:26:50.017: Device reported verify completion 202s (process:4495): libfprint-device-DEBUG: 20:26:50.017: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:4495): libfprint-device-DEBUG: 20:26:50.017: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 202s (process:4495): libfprint-device-DEBUG: 20:26:50.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.218: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.218: Got instructions of length 16 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.218: Received command SET_KEEP_ALIVE 0 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.218: Keep alive toggled: 0 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.218: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.218: Got instructions of length 19 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.218: Received command SET_ENROLL_STAGES 5 202s (process:4495): libfprint-device-DEBUG: 20:26:50.218: Device reported close completion 202s (process:4495): libfprint-device-DEBUG: 20:26:50.218: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 202s (process:4495): libfprint-device-DEBUG: 20:26:50.218: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s ok 202s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.218: 170014186: ../libfprint/drivers/virtual-device.c:387 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.218: 170014202: ../libfprint/drivers/virtual-device-listener.c:153 202s (process:4495): libfprint-device-DEBUG: 20:26:50.218: Device reported open completion 202s (process:4495): libfprint-device-DEBUG: 20:26:50.218: Completing action FPI_DEVICE_ACTION_OPEN in idle! 202s (process:4495): libfprint-device-DEBUG: 20:26:50.218: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.218: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Got instructions of length 14 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Received command SCAN foo-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Processing command SCAN foo-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported enroll progress, reported 1 of 5 have been completed 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Sleeping completed 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.219: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Got instructions of length 14 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Received command SCAN foo-print 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Processing command SCAN foo-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported enroll progress, reported 2 of 5 have been completed 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Sleeping completed 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.219: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Got instructions of length 14 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Received command SCAN foo-print 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Processing command SCAN foo-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported enroll progress, reported 3 of 5 have been completed 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Sleeping completed 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.219: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Got instructions of length 14 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Received command SCAN foo-print 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.219: Processing command SCAN foo-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Device reported enroll progress, reported 4 of 5 have been completed 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Sleeping completed 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.220: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Got instructions of length 14 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Received command SCAN foo-print 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Processing command SCAN foo-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Device reported enroll progress, reported 5 of 5 have been completed 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Device reported enroll completion 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Device reported finger status change: FP_FINGER_STATUS_NONE 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Print for finger FP_FINGER_LEFT_RING enrolled 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.220: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Got instructions of length 9 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Received command SLEEP 100 202s (process:4495): libfprint-device-DEBUG: 20:26:50.220: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Processing command SLEEP 100 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Sleeping 100ms 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.220: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Got instructions of length 14 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Received command SCAN bar-print 202s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:50.220: Got a new connection! 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Got instructions of length 9 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.220: Received command SLEEP 800 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.320: Sleeping completed 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.320: Processing command SCAN bar-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-device-DEBUG: 20:26:50.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.320: Virtual device scanned print bar-print 202s (process:4495): libfprint-device-DEBUG: 20:26:50.320: Device reported verify result 202s (process:4495): libfprint-device-DEBUG: 20:26:50.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.320: Processing command SLEEP 800 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.320: Sleeping 800ms 202s (process:4495): libfprint-virtual_device-DEBUG: 20:26:50.320: Sleeping now, command queued for later: SCAN bar-print 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.121: Sleeping completed 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.121: Processing command SCAN bar-print 203s (process:4495): libfprint-device-DEBUG: 20:26:51.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.121: Virtual device scanned print bar-print 203s (process:4495): libfprint-device-DEBUG: 20:26:51.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 203s (process:4495): libfprint-device-DEBUG: 20:26:51.121: Device reported verify completion 203s (process:4495): libfprint-device-DEBUG: 20:26:51.121: Device reported finger status change: FP_FINGER_STATUS_NONE 203s (process:4495): libfprint-device-DEBUG: 20:26:51.121: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 203s (process:4495): libfprint-device-DEBUG: 20:26:51.121: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:51.122: Got a new connection! 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Got instructions of length 16 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Received command SET_KEEP_ALIVE 0 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Keep alive toggled: 0 203s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:51.122: Got a new connection! 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Got instructions of length 19 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Received command SET_ENROLL_STAGES 5 203s (process:4495): libfprint-device-DEBUG: 20:26:51.122: Device reported close completion 203s (process:4495): libfprint-device-DEBUG: 20:26:51.122: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 203s (process:4495): libfprint-device-DEBUG: 20:26:51.122: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s Enroll done 203s ok 203s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: 170918119: ../libfprint/drivers/virtual-device.c:387 203s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:51.122: 170918134: ../libfprint/drivers/virtual-device-listener.c:153 203s (process:4495): libfprint-device-DEBUG: 20:26:51.122: Device reported open completion 203s (process:4495): libfprint-device-DEBUG: 20:26:51.122: Completing action FPI_DEVICE_ACTION_OPEN in idle! 203s (process:4495): libfprint-device-DEBUG: 20:26:51.122: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:51.122: Got a new connection! 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Got instructions of length 26 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Received command SET_CANCELLATION_ENABLED 0 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Cancellation support toggled: 0 203s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:51.122: Got a new connection! 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Got instructions of length 10 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.122: Received command SLEEP 1500 203s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:51.123: Got a new connection! 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.123: Got instructions of length 14 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.123: Received command SCAN foo-print 203s (process:4495): libfprint-device-DEBUG: 20:26:51.123: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.123: Processing command SLEEP 1500 203s (process:4495): libfprint-virtual_device-DEBUG: 20:26:51.123: Sleeping 1500ms 203s (process:4495): libfprint-device-DEBUG: 20:26:51.423: Idle cancelling on ongoing operation! 204s Executing: libfprint-2/virtual-device.test 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.624: Sleeping completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.624: Virtual device scan failed with error: Operation was cancelled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.624: Processing command SCAN foo-print 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.624: 172420384: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.624: 172420402: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.624: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.625: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Received command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported enroll progress, reported 1 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.625: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.625: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported enroll progress, reported 3 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.625: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.625: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.625: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.625: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Device reported enroll progress, reported 5 of 5 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Print for finger FP_FINGER_LEFT_LITTLE enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.626: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.626: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s ok 204s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: 172422259: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.626: 172422266: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.626: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.626: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Received command SET_ENROLL_STAGES 8 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.626: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.626: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command RETRY 1 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command RETRY 3 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command RETRY 2 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.627: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.627: Received command SLEEP 10 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.628: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Received command SLEEP 20 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.628: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Received command RETRY 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.628: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Received command RETRY 3 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.628: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.628: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Got instructions of length 15 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Received command SCAN another-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.628: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.628: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Received command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported enroll progress, reported 1 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported enroll progress, reported 2 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Processing command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported enroll progress, reported 2 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported enroll progress, reported 3 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Processing command RETRY 3 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported enroll progress, reported 3 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.628: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.629: Device reported enroll progress, reported 4 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.629: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.629: Processing command RETRY 2 204s (process:4495): libfprint-device-DEBUG: 20:26:52.629: Device reported enroll progress, reported 4 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.629: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.629: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.629: Device reported enroll progress, reported 5 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.629: Processing command SLEEP 10 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.629: Sleeping 10ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.639: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.639: Processing command SLEEP 20 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.639: Sleeping 20ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Processing command RETRY 0 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported enroll progress, reported 5 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Processing command RETRY 3 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported enroll progress, reported 5 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported enroll progress, reported 6 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Processing command SCAN another-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported enroll progress, reported 6 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported enroll progress, reported 7 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported enroll progress, reported 8 of 8 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Print for finger FP_FINGER_UNKNOWN enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.659: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.659: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.659: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.660: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.660: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.660: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.660: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: 172455900: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.660: 172455913: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.660: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.660: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.660: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.660: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: Received command SLEEP 50 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.660: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.660: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.660: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.661: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Received command RETRY 1 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.661: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.661: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Received command SLEEP 50 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.661: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.661: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.661: Received command RETRY 2 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.661: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.662: Got instructions of length 15 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.662: Received command SCAN another-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.662: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.662: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.662: Received command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.662: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.662: Processing command SLEEP 50 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.662: Sleeping 50ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported enroll progress, reported 1 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Processing command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.712: Device reported enroll progress, reported 3 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Processing command SLEEP 50 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.712: Sleeping 50ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.762: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.762: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.762: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.762: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.762: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.762: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.762: Processing command RETRY 2 204s (process:4495): libfprint-device-DEBUG: 20:26:52.762: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Processing command SCAN another-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported enroll progress, reported 5 of 5 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Print for finger FP_FINGER_UNKNOWN enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.763: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.763: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: 172559342: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.763: 172559355: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.763: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.763: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.763: Received command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported enroll progress, reported 1 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.764: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.764: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported enroll progress, reported 3 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.764: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.764: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.764: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported enroll progress, reported 5 of 5 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Print for finger FP_FINGER_LEFT_RING enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.764: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.764: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Received command ERROR 0 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Processing command ERROR 0 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Virtual device scan failed with error: An unspecified error occurred! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.765: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.765: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s ok 204s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: 172561222: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.765: 172561230: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.765: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Received command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.765: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.765: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported enroll progress, reported 1 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.766: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.766: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported enroll progress, reported 3 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.766: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.766: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.766: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported enroll progress, reported 5 of 5 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Print for finger FP_FINGER_LEFT_THUMB enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.766: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.767: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Received command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Virtual device scanned print testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported verify result 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.767: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.767: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s ok 204s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: 172563213: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.767: 172563222: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.767: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Received command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.767: Device reported enroll progress, reported 1 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.767: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.767: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.768: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported enroll progress, reported 3 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.768: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.768: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported enroll progress, reported 5 of 5 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Print for finger FP_FINGER_LEFT_RING enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.768: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Got instructions of length 18 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Received command SCAN not-testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Processing command SCAN not-testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.768: Virtual device scanned print not-testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported verify result 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.768: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.769: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.769: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s ok 204s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: 172565026: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.769: 172565037: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.769: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Received command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Processing command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Virtual device scan failed with error: The swipe was too short, please try again. 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Device reported verify result 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.769: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.769: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.769: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.769: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.770: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.770: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.770: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: 172565758: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.770: 172565766: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.770: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.770: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.770: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.770: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Received command SET_ENROLL_STAGES 8 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.770: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.770: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.770: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.770: Received command RETRY 1 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.770: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command RETRY 3 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command RETRY 2 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command SLEEP 10 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command SLEEP 20 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command RETRY 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.771: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.771: Received command RETRY 3 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.772: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.772: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Got instructions of length 15 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Received command SCAN another-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.772: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Received command SCAN print-id 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.772: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Received command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 1 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 2 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 2 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 3 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command RETRY 3 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 3 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 4 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command RETRY 2 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 4 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.772: Device reported enroll progress, reported 5 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Processing command SLEEP 10 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.772: Sleeping 10ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.782: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.782: Processing command SLEEP 20 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.782: Sleeping 20ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Processing command RETRY 0 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported enroll progress, reported 5 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Processing command RETRY 3 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported enroll progress, reported 5 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported enroll progress, reported 6 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Processing command SCAN another-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported enroll progress, reported 6 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported enroll progress, reported 7 of 8 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.802: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported enroll progress, reported 8 of 8 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Print for finger FP_FINGER_UNKNOWN enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.802: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.803: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Received command RETRY 2 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Processing command RETRY 2 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Virtual device scan failed with error: The finger was not centered properly, please try again. 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Device reported verify result 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.803: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Received command SLEEP 50 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.803: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Received command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.803: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Processing command SLEEP 50 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.803: Sleeping 50ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.853: Sleeping completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.853: Processing command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.853: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.853: Virtual device scan failed with error: The swipe was too short, please try again. 204s (process:4495): libfprint-device-DEBUG: 20:26:52.853: Device reported verify result 204s (process:4495): libfprint-device-DEBUG: 20:26:52.853: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.853: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.853: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.853: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.854: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Got instructions of length 15 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Received command SCAN another-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Processing command SCAN another-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Virtual device scanned print another-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported verify result 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.854: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Got instructions of length 13 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Received command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Processing command SCAN print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Virtual device scanned print print-id 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported verify result 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.854: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.854: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.854: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.854: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: 172650661: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.855: 172650673: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.855: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Received command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported enroll progress, reported 1 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.855: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.855: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Received command RETRY 1 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Processing command RETRY 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported enroll progress, reported 2 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.855: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.855: Device reported enroll progress, reported 3 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.855: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.856: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported enroll progress, reported 4 of 5 have been completed 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Sleeping completed 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.856: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Received command SCAN testprint 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported enroll progress, reported 5 of 5 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Print for finger FP_FINGER_LEFT_LITTLE enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.856: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.856: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s ok 204s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.856: 172652400: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.856: 172652410: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-device-DEBUG: 20:26:52.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.857: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Received command FINGER 1 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Processing command FINGER 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.857: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Received command FINGER 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Processing command FINGER 0 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Idle cancelling on ongoing operation! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Got cancellation! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Virtual device scan failed with error: Operation was cancelled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.857: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.857: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: 172653328: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.857: 172653338: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.857: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Received command SLEEP 10 204s (process:4495): libfprint-device-DEBUG: 20:26:52.857: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Processing command SLEEP 10 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.857: Sleeping 10ms 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Sleeping completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.868: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Received command FINGER 1 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Processing command FINGER 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.868: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Got instructions of length 8 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Received command FINGER 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Processing command FINGER 0 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Idle cancelling on ongoing operation! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Got cancellation! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Virtual device scan failed with error: Operation was cancelled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Device reported verify completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.868: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.868: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.868: 172664431: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.868: 172664441: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.868: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.869: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.869: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: 172665073: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.869: 172665085: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.869: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Received command IGNORED_COMMAND 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.869: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Received command ERROR 5 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Processing command IGNORED_COMMAND 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.869: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: 172665597: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.869: Processing command ERROR 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: 172665693: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.870: 172665704: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.870: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Received command SET_KEEP_ALIVE 1 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Keep alive toggled: 1 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.870: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Got instructions of length 7 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Received command ERROR 5 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: 172666098: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Processing command ERROR 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s ok 204s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: 172666181: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.870: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Received command SET_ENROLL_STAGES 1 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.870: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Got instructions of length 14 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Received command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.870: Processing command SCAN testprint 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported enroll progress, reported 1 of 1 have been completed 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported enroll completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Device reported finger status change: FP_FINGER_STATUS_NONE 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Print for finger FP_FINGER_LEFT_LITTLE enrolled 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.871: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.871: Got instructions of length 16 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.871: Received command SET_KEEP_ALIVE 0 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.871: Keep alive toggled: 0 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.871: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.871: Got instructions of length 19 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.871: Received command SET_ENROLL_STAGES 5 204s (process:4495): libfprint-device-DEBUG: 20:26:52.871: Device reported close completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.871: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 204s Enroll done 204s ok 204s (process:4495): libfprint-context-DEBUG: 20:26:52.871: Initializing FpContext (libfprint version 1.94.8+tod1) 204s (process:4495): libfprint-tod-DEBUG: 20:26:52.871: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 204s (process:4495): libfprint-context-DEBUG: 20:26:52.872: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-9o2ca3s9/virtual-device.socket 204s (process:4495): libfprint-context-DEBUG: 20:26:52.872: created 204s (process:4495): libfprint-device-DEBUG: 20:26:52.872: Device reported probe completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.872: Completing action FPI_DEVICE_ACTION_PROBE in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.872: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.872: 172668027: ../libfprint/drivers/virtual-device.c:387 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.872: 172668040: ../libfprint/drivers/virtual-device-listener.c:153 204s (process:4495): libfprint-device-DEBUG: 20:26:52.872: Device reported open completion 204s (process:4495): libfprint-device-DEBUG: 20:26:52.872: Completing action FPI_DEVICE_ACTION_OPEN in idle! 204s (process:4495): libfprint-device-DEBUG: 20:26:52.872: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 204s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:52.872: Got a new connection! 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.872: Got instructions of length 9 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.872: Received command SLEEP 200 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.872: Processing command SLEEP 200 204s (process:4495): libfprint-virtual_device-DEBUG: 20:26:52.872: Sleeping 200ms 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.072: Sleeping completed 205s (process:4495): libfprint-device-DEBUG: 20:26:53.073: Device reported close completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.073: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.073: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.073: 172868950: ../libfprint/drivers/virtual-device.c:387 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.073: 172868962: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:4495): libfprint-device-DEBUG: 20:26:53.073: Device reported open completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.073: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.073: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.073: Got a new connection! 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.073: Got instructions of length 9 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.073: Received command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.073: Processing command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.073: Sleeping 200ms 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.274: Sleeping completed 205s (process:4495): libfprint-device-DEBUG: 20:26:53.274: Device reported close completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.274: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.274: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.274: 173070040: ../libfprint/drivers/virtual-device.c:387 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.274: 173070055: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:4495): libfprint-device-DEBUG: 20:26:53.274: Device reported open completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.274: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.274: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.274: Got a new connection! 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.274: Got instructions of length 9 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.274: Received command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.274: Processing command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.274: Sleeping 200ms 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.475: Sleeping completed 205s (process:4495): libfprint-device-DEBUG: 20:26:53.475: Device reported close completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.475: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.475: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.475: 173271071: ../libfprint/drivers/virtual-device.c:387 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.475: 173271087: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:4495): libfprint-device-DEBUG: 20:26:53.475: Device reported open completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.475: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.475: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.475: Got a new connection! 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.475: Got instructions of length 9 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.475: Received command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.475: Processing command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.475: Sleeping 200ms 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.676: Sleeping completed 205s (process:4495): libfprint-device-DEBUG: 20:26:53.676: Device reported close completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.676: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.676: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.676: 173472087: ../libfprint/drivers/virtual-device.c:387 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.676: 173472102: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:4495): libfprint-device-DEBUG: 20:26:53.676: Device reported open completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.676: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.676: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.676: Got a new connection! 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.676: Got instructions of length 9 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.676: Received command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.676: Processing command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.676: Sleeping 200ms 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.877: Sleeping completed 205s (process:4495): libfprint-device-DEBUG: 20:26:53.877: Device reported close completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.877: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.877: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s ok 205s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.877: 173673157: ../libfprint/drivers/virtual-device.c:387 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.877: 173673169: ../libfprint/drivers/virtual-device-listener.c:153 205s (process:4495): libfprint-device-DEBUG: 20:26:53.877: Device reported open completion 205s (process:4495): libfprint-device-DEBUG: 20:26:53.877: Completing action FPI_DEVICE_ACTION_OPEN in idle! 205s (process:4495): libfprint-device-DEBUG: 20:26:53.877: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 205s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:53.877: Got a new connection! 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.877: Got instructions of length 9 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.877: Received command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.877: Processing command SLEEP 200 205s (process:4495): libfprint-virtual_device-DEBUG: 20:26:53.877: Sleeping 200ms 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.078: Sleeping completed 206s (process:4495): libfprint-device-DEBUG: 20:26:54.078: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.078: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.078: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.078: 173874227: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.078: 173874237: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.078: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.078: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.078: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.078: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.078: Got instructions of length 9 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.078: Received command SLEEP 200 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.079: Processing command SLEEP 200 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.079: Sleeping 200ms 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.079: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.079: Got instructions of length 16 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.079: Received command SET_KEEP_ALIVE 1 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.079: Keep alive toggled: 1 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.279: Sleeping completed 206s (process:4495): libfprint-device-DEBUG: 20:26:54.279: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.279: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.279: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.279: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.279: Got instructions of length 9 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.279: Received command SLEEP 100 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.279: 174075452: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.279: Processing command SLEEP 100 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.279: Sleeping 100ms 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.380: Sleeping completed 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.380: 174175687: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.380: 174175895: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.380: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.380: Got instructions of length 9 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.380: Received command SLEEP 200 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.380: Processing command SLEEP 200 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.380: Sleeping 200ms 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.580: Sleeping completed 206s (process:4495): libfprint-device-DEBUG: 20:26:54.580: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.580: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.581: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.581: 174376937: ../libfprint/drivers/virtual-device.c:752 206s (process:4495): libfprint-context-DEBUG: 20:26:54.581: Initializing FpContext (libfprint version 1.94.8+tod1) 206s (process:4495): libfprint-tod-DEBUG: 20:26:54.581: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 206s (process:4495): libfprint-context-DEBUG: 20:26:54.582: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-apdzu_yc/virtual-device.socket 206s (process:4495): libfprint-context-DEBUG: 20:26:54.582: created 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Device reported probe completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Completing action FPI_DEVICE_ACTION_PROBE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.582: 174378203: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.582: 174378230: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.582: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.583: 174378609: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.583: 174378634: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.583: 174378989: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.583: 174379040: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.583: 174379257: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.583: 174379263: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.583: 174379451: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.583: 174379458: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.583: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.584: 174379649: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.584: 174379656: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.584: 174379825: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.584: 174379831: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.584: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.584: 174380155: ../libfprint/drivers/virtual-device.c:752 206s (process:4495): libfprint-context-DEBUG: 20:26:54.584: Initializing FpContext (libfprint version 1.94.8+tod1) 206s (process:4495): libfprint-tod-DEBUG: 20:26:54.584: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 206s (process:4495): libfprint-context-DEBUG: 20:26:54.585: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-apdzu_yc/virtual-device.socket 206s (process:4495): libfprint-context-DEBUG: 20:26:54.585: created 206s (process:4495): libfprint-context-DEBUG: 20:26:54.585: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-39lvlzp_/virtual-device-storage.socket 206s (process:4495): libfprint-context-DEBUG: 20:26:54.585: created 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Device reported probe completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Device reported probe completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Completing action FPI_DEVICE_ACTION_PROBE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Completing action FPI_DEVICE_ACTION_PROBE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.585: 174381315: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.585: 174381342: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.585: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.585: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Got instructions of length 5 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Received command CONT 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Processing command CONT 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Device reported deletion completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.586: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Got instructions of length 16 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Received command SET_KEEP_ALIVE 0 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Keep alive toggled: 0 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.586: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Got instructions of length 19 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: Received command SET_ENROLL_STAGES 5 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.586: 174382423: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.586: 174382442: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.586: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.587: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Got instructions of length 20 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Received command SET_ENROLL_STAGES 20 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.587: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Got instructions of length 19 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Received command SET_ENROLL_STAGES 1 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.587: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Got instructions of length 19 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Received command SET_ENROLL_STAGES 0 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.587: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Got instructions of length 5 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Received command CONT 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.587: Processing command CONT 206s (process:4495): libfprint-device-DEBUG: 20:26:54.587: Device reported deletion completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.587: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.587: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.588: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: Got instructions of length 16 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: Received command SET_KEEP_ALIVE 0 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: Keep alive toggled: 0 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.588: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: Got instructions of length 19 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: Received command SET_ENROLL_STAGES 5 206s (process:4495): libfprint-device-DEBUG: 20:26:54.588: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.588: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.588: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: 174384182: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.588: 174384204: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.588: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.588: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.588: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.588: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: Got instructions of length 19 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.588: Received command SET_SCAN_TYPE press 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.589: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Got instructions of length 19 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Received command SET_SCAN_TYPE swipe 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.589: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Got instructions of length 25 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Received command SET_SCAN_TYPE eye-contact 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.589: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Got instructions of length 5 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Received command CONT 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Processing command CONT 206s (process:4495): libfprint-device-DEBUG: 20:26:54.589: Device reported deletion completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.589: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.589: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.589: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Got instructions of length 16 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Received command SET_KEEP_ALIVE 0 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.589: Keep alive toggled: 0 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.589: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.590: Got instructions of length 19 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.590: Received command SET_ENROLL_STAGES 5 206s (process:4495): libfprint-device-DEBUG: 20:26:54.590: Device reported close completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.590: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.590: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s ok 206s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.590: 174385907: ../libfprint/drivers/virtual-device.c:387 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.590: 174385926: ../libfprint/drivers/virtual-device-listener.c:153 206s (process:4495): libfprint-device-DEBUG: 20:26:54.590: Device reported open completion 206s (process:4495): libfprint-device-DEBUG: 20:26:54.590: Completing action FPI_DEVICE_ACTION_OPEN in idle! 206s (process:4495): libfprint-device-DEBUG: 20:26:54.590: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 206s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:54.590: Got a new connection! 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.590: Got instructions of length 9 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.590: Received command INSERT p1 206s (process:4495): libfprint-virtual_device-DEBUG: 20:26:54.590: Processing command INSERT p1 207s (process:4495): libfprint-device-DEBUG: 20:26:55.091: Device reported listing completion 207s (process:4495): libfprint-device-DEBUG: 20:26:55.091: Completing action FPI_DEVICE_ACTION_LIST in idle! 207s (process:4495): libfprint-device-DEBUG: 20:26:55.091: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:55.091: Got a new connection! 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.091: Got instructions of length 5 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.091: Received command CONT 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.091: Processing command CONT 207s (process:4495): libfprint-device-DEBUG: 20:26:55.091: Device reported deletion completion 207s (process:4495): libfprint-device-DEBUG: 20:26:55.091: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 207s (process:4495): libfprint-device-DEBUG: 20:26:55.091: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:4495): libfprint-device-DEBUG: 20:26:55.592: Device reported listing completion 207s (process:4495): libfprint-device-DEBUG: 20:26:55.594: Completing action FPI_DEVICE_ACTION_LIST in idle! 207s (process:4495): libfprint-device-DEBUG: 20:26:55.594: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:55.594: Got a new connection! 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.594: Got instructions of length 5 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.594: Received command CONT 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.594: Processing command CONT 207s (process:4495): libfprint-device-DEBUG: 20:26:55.594: Device reported deletion completion 207s (process:4495): libfprint-device-DEBUG: 20:26:55.594: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 207s (process:4495): libfprint-device-DEBUG: 20:26:55.594: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:55.594: Got a new connection! 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.594: Got instructions of length 16 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.594: Received command SET_KEEP_ALIVE 0 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.594: Keep alive toggled: 0 207s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:55.595: Got a new connection! 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.595: Got instructions of length 19 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.595: Received command SET_ENROLL_STAGES 5 207s (process:4495): libfprint-device-DEBUG: 20:26:55.595: Device reported close completion 207s (process:4495): libfprint-device-DEBUG: 20:26:55.595: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 207s (process:4495): libfprint-device-DEBUG: 20:26:55.595: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s 207s ok 207s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.595: 175390952: ../libfprint/drivers/virtual-device.c:387 207s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:55.595: 175390978: ../libfprint/drivers/virtual-device-listener.c:153 207s (process:4495): libfprint-device-DEBUG: 20:26:55.595: Device reported open completion 207s (process:4495): libfprint-device-DEBUG: 20:26:55.595: Completing action FPI_DEVICE_ACTION_OPEN in idle! 207s (process:4495): libfprint-device-DEBUG: 20:26:55.595: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 207s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:55.595: Got a new connection! 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.595: Got instructions of length 9 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.595: Received command INSERT p1 207s (process:4495): libfprint-virtual_device-DEBUG: 20:26:55.596: Processing command INSERT p1 208s (process:4495): libfprint-device-DEBUG: 20:26:56.096: Device reported listing completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.096: Completing action FPI_DEVICE_ACTION_LIST in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.096: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.096: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.096: Got instructions of length 7 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Received command ERROR 5 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Processing command ERROR 5 208s (process:4495): libfprint-device-DEBUG: 20:26:56.097: Device reported deletion completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.097: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.097: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.097: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Got instructions of length 5 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Received command CONT 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Processing command CONT 208s (process:4495): libfprint-device-DEBUG: 20:26:56.097: Device reported deletion completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.097: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.097: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.097: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Got instructions of length 16 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Received command SET_KEEP_ALIVE 0 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.097: Keep alive toggled: 0 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.097: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.098: Got instructions of length 19 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.098: Received command SET_ENROLL_STAGES 5 208s (process:4495): libfprint-device-DEBUG: 20:26:56.098: Device reported close completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.098: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.098: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s 208s ok 208s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.098: 175894033: ../libfprint/drivers/virtual-device.c:387 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.098: 175894074: ../libfprint/drivers/virtual-device-listener.c:153 208s (process:4495): libfprint-device-DEBUG: 20:26:56.098: Device reported open completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.098: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.098: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.098: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.098: Got instructions of length 9 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.098: Received command SLEEP 100 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.098: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.099: Got instructions of length 7 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.099: Received command ERROR 4 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.099: Processing command SLEEP 100 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.099: Sleeping 100ms 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.199: Sleeping completed 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.199: Processing command ERROR 4 208s (process:4495): libfprint-device-DEBUG: 20:26:56.199: Device reported close completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.199: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.199: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s ok 208s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.200: 175995629: ../libfprint/drivers/virtual-device.c:387 208s (process:4495): libfprint-device-DEBUG: 20:26:56.200: Device reported open completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.200: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.200: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.200: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.200: Got instructions of length 16 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.200: Received command SET_KEEP_ALIVE 1 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.200: Keep alive toggled: 1 208s (process:4495): libfprint-device-DEBUG: 20:26:56.200: Device reported close completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.200: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.200: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.201: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.201: Got instructions of length 9 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.201: Received command SLEEP 500 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.201: 175996777: ../libfprint/drivers/virtual-device.c:387 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.201: Processing command SLEEP 500 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.201: Sleeping 500ms 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.701: Sleeping completed 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.701: 176497395: ../libfprint/drivers/virtual-device.c:387 208s (process:4495): libfprint-device-DEBUG: 20:26:56.701: Device reported open completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.701: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.701: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.702: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Got instructions of length 5 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Received command CONT 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Processing command CONT 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Device reported deletion completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.702: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Got instructions of length 16 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Received command SET_KEEP_ALIVE 0 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Keep alive toggled: 0 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.702: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Got instructions of length 19 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Received command SET_ENROLL_STAGES 5 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Device reported close completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s ok 208s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: 176498229: ../libfprint/drivers/virtual-device.c:387 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.702: 176498243: ../libfprint/drivers/virtual-device-listener.c:153 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Device reported open completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Completing action FPI_DEVICE_ACTION_OPEN in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.702: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.702: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Got instructions of length 16 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Received command IGNORED_COMMAND 208s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:56.702: Got a new connection! 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Got instructions of length 9 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.702: Received command SLEEP 500 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.703: Processing command IGNORED_COMMAND 208s (process:4495): libfprint-device-DEBUG: 20:26:56.703: Device reported close completion 208s (process:4495): libfprint-device-DEBUG: 20:26:56.703: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 208s (process:4495): libfprint-device-DEBUG: 20:26:56.703: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.703: 176498834: ../libfprint/drivers/virtual-device.c:387 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.703: Processing command SLEEP 500 208s (process:4495): libfprint-virtual_device-DEBUG: 20:26:56.703: Sleeping 500ms 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.203: Sleeping completed 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.203: 176999448: ../libfprint/drivers/virtual-device.c:387 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.203: 176999462: ../libfprint/drivers/virtual-device-listener.c:153 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Device reported open completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.204: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Got instructions of length 5 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Received command CONT 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Processing command CONT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Device reported deletion completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.204: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Received command SET_KEEP_ALIVE 0 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Keep alive toggled: 0 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.204: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Got instructions of length 19 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: Received command SET_ENROLL_STAGES 5 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Device reported close completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 209s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.204: 177000466: ../libfprint/drivers/virtual-device.c:387 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.204: 177000473: ../libfprint/drivers/virtual-device-listener.c:153 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Device reported open completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.204: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.205: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: Received command SET_KEEP_ALIVE 1 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: Keep alive toggled: 1 209s (process:4495): libfprint-device-DEBUG: 20:26:57.205: Device reported close completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.205: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.205: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.205: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: Got instructions of length 9 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: Received command SLEEP 500 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: 177000899: ../libfprint/drivers/virtual-device.c:387 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: Processing command SLEEP 500 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.205: Sleeping 500ms 209s Executing: libfprint-2/virtual-device.test 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.705: Sleeping completed 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.705: 177501486: ../libfprint/drivers/virtual-device.c:387 209s (process:4495): libfprint-device-DEBUG: 20:26:57.705: Device reported open completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.705: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.705: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.706: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Got instructions of length 5 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Received command CONT 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Processing command CONT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.706: Device reported deletion completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.706: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.706: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.706: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Received command SET_KEEP_ALIVE 0 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Keep alive toggled: 0 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.706: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Got instructions of length 19 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: Received command SET_ENROLL_STAGES 5 209s (process:4495): libfprint-device-DEBUG: 20:26:57.706: Device reported close completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.706: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.706: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 209s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.706: 177502526: ../libfprint/drivers/virtual-device.c:387 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.706: 177502540: ../libfprint/drivers/virtual-device-listener.c:153 209s (process:4495): libfprint-device-DEBUG: 20:26:57.707: Device reported open completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.707: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.707: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.707: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.707: Got instructions of length 9 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.707: Received command SLEEP 100 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.707: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.707: Got instructions of length 7 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.707: Received command ERROR 7 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.707: Processing command SLEEP 100 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.707: Sleeping 100ms 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.807: Sleeping completed 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.807: Processing command ERROR 7 209s (process:4495): libfprint-device-DEBUG: 20:26:57.807: Device reported deletion completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.807: Completing action FPI_DEVICE_ACTION_DELETE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.807: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.808: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Got instructions of length 5 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Received command CONT 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Processing command CONT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Device reported deletion completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.808: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Received command SET_KEEP_ALIVE 0 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Keep alive toggled: 0 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.808: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Got instructions of length 19 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Received command SET_ENROLL_STAGES 5 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Device reported close completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s ok 209s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: 177604271: ../libfprint/drivers/virtual-device.c:387 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.808: 177604283: ../libfprint/drivers/virtual-device-listener.c:153 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Device reported open completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Completing action FPI_DEVICE_ACTION_OPEN in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.808: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Received command SCAN right-thumb 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.808: Processing command SCAN right-thumb 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED 209s (process:4495): libfprint-device-DEBUG: 20:26:57.808: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported enroll progress, reported 1 of 5 have been completed 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Sleeping completed 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.809: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Received command SCAN right-thumb 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Processing command SCAN right-thumb 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported enroll progress, reported 2 of 5 have been completed 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Sleeping completed 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.809: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Received command SCAN right-thumb 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Processing command SCAN right-thumb 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported enroll progress, reported 3 of 5 have been completed 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Sleeping completed 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.809: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Received command SCAN right-thumb 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Processing command SCAN right-thumb 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported enroll progress, reported 4 of 5 have been completed 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Sleeping completed 209s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:57.809: Got a new connection! 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Got instructions of length 16 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Received command SCAN right-thumb 209s (process:4495): libfprint-virtual_device-DEBUG: 20:26:57.809: Processing command SCAN right-thumb 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported enroll progress, reported 5 of 5 have been completed 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported enroll completion 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Device reported finger status change: FP_FINGER_STATUS_NONE 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Print for finger FP_FINGER_RIGHT_THUMB enrolled 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 209s (process:4495): libfprint-device-DEBUG: 20:26:57.809: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:26:58.310: Deleting print right-thumb for user testuser 210s (process:4495): libfprint-device-DEBUG: 20:26:58.310: Device reported deletion completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.310: Completing action FPI_DEVICE_ACTION_DELETE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.310: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:26:58.811: Deleting print right-thumb for user testuser 210s (process:4495): libfprint-device-DEBUG: 20:26:58.811: Device reported deletion completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.811: Completing action FPI_DEVICE_ACTION_DELETE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.811: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.811: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.811: Got instructions of length 5 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.811: Received command CONT 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.811: Processing command CONT 210s (process:4495): libfprint-device-DEBUG: 20:26:58.811: Device reported deletion completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.811: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.811: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.812: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.812: Got instructions of length 16 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.812: Received command SET_KEEP_ALIVE 0 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.812: Keep alive toggled: 0 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.812: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.812: Got instructions of length 19 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.812: Received command SET_ENROLL_STAGES 5 210s (process:4495): libfprint-device-DEBUG: 20:26:58.812: Device reported close completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.812: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.812: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s Enroll done 210s ok 210s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.812: 178608240: ../libfprint/drivers/virtual-device.c:387 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.812: 178608263: ../libfprint/drivers/virtual-device-listener.c:153 210s (process:4495): libfprint-device-DEBUG: 20:26:58.812: Device reported open completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.812: Completing action FPI_DEVICE_ACTION_OPEN in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.812: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.812: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Got instructions of length 5 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Received command CONT 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Processing command CONT 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Device reported deletion completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.813: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Got instructions of length 16 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Received command SET_KEEP_ALIVE 0 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Keep alive toggled: 0 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.813: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Got instructions of length 19 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: Received command SET_ENROLL_STAGES 5 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Device reported close completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s ok 210s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.813: 178609393: ../libfprint/drivers/virtual-device.c:387 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.813: 178609416: ../libfprint/drivers/virtual-device-listener.c:153 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Device reported open completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Completing action FPI_DEVICE_ACTION_OPEN in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.813: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.814: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Got instructions of length 5 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Received command CONT 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Processing command CONT 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Device reported deletion completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.814: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Got instructions of length 16 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Received command SET_KEEP_ALIVE 0 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Keep alive toggled: 0 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.814: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Got instructions of length 19 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Received command SET_ENROLL_STAGES 5 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Device reported close completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s ok 210s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: 178609969: ../libfprint/drivers/virtual-device.c:387 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.814: 178609975: ../libfprint/drivers/virtual-device-listener.c:153 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Device reported open completion 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Completing action FPI_DEVICE_ACTION_OPEN in idle! 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:58.814: Got a new connection! 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Got instructions of length 10 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Received command SLEEP 1500 210s (process:4495): libfprint-device-DEBUG: 20:26:58.814: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Processing command SLEEP 1500 210s (process:4495): libfprint-virtual_device-DEBUG: 20:26:58.814: Sleeping 1500ms 211s (process:4495): libfprint-device-DEBUG: 20:26:59.114: Idle cancelling on ongoing operation! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.115: Got cancellation! 211s (process:4495): libfprint-device-DEBUG: 20:26:59.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.115: Device reported identify completion 211s (process:4495): libfprint-device-DEBUG: 20:26:59.115: Device reported finger status change: FP_FINGER_STATUS_NONE 211s (process:4495): libfprint-device-DEBUG: 20:26:59.115: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 211s (process:4495): libfprint-device-DEBUG: 20:26:59.115: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.315: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Got instructions of length 5 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Received command CONT 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Processing command CONT 211s (process:4495): libfprint-device-DEBUG: 20:26:59.315: Device reported deletion completion 211s (process:4495): libfprint-device-DEBUG: 20:26:59.315: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 211s (process:4495): libfprint-device-DEBUG: 20:26:59.315: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.315: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Got instructions of length 16 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Received command SET_KEEP_ALIVE 0 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Keep alive toggled: 0 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.315: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Got instructions of length 19 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.315: Received command SET_ENROLL_STAGES 5 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Device reported close completion 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 211s ok 211s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.316: 179111850: ../libfprint/drivers/virtual-device.c:387 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.316: 179111870: ../libfprint/drivers/virtual-device-listener.c:153 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Device reported open completion 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Completing action FPI_DEVICE_ACTION_OPEN in idle! 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.316: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.316: Got instructions of length 14 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.316: Received command SCAN foo-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.316: Processing command SCAN foo-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.316: Device reported enroll progress, reported 1 of 5 have been completed 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.316: Sleeping completed 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.316: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Got instructions of length 14 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Received command SCAN foo-print 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Processing command SCAN foo-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported enroll progress, reported 2 of 5 have been completed 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Sleeping completed 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.317: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Got instructions of length 14 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Received command SCAN foo-print 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Processing command SCAN foo-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported enroll progress, reported 3 of 5 have been completed 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Sleeping completed 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.317: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Got instructions of length 14 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Received command SCAN foo-print 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Processing command SCAN foo-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported enroll progress, reported 4 of 5 have been completed 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Sleeping completed 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.317: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Got instructions of length 14 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Received command SCAN foo-print 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.317: Processing command SCAN foo-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported enroll progress, reported 5 of 5 have been completed 211s (process:4495): libfprint-device-DEBUG: 20:26:59.317: Device reported enroll completion 211s (process:4495): libfprint-device-DEBUG: 20:26:59.318: Device reported finger status change: FP_FINGER_STATUS_NONE 211s (process:4495): libfprint-device-DEBUG: 20:26:59.318: Print for finger FP_FINGER_LEFT_RING enrolled 211s (process:4495): libfprint-device-DEBUG: 20:26:59.318: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 211s (process:4495): libfprint-device-DEBUG: 20:26:59.318: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.318: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Got instructions of length 9 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Received command SLEEP 100 211s (process:4495): libfprint-device-DEBUG: 20:26:59.318: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Processing command SLEEP 100 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Sleeping 100ms 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.318: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Got instructions of length 14 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Received command SCAN bar-print 211s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:26:59.318: Got a new connection! 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Got instructions of length 9 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.318: Received command SLEEP 800 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.418: Sleeping completed 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.418: Processing command SCAN bar-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.418: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-device-DEBUG: 20:26:59.418: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 211s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:26:59.418: Trying to identify print 'bar-print' against a gallery of 1 prints 211s (process:4495): libfprint-device-DEBUG: 20:26:59.418: Device reported identify result 211s (process:4495): libfprint-device-DEBUG: 20:26:59.418: Device reported finger status change: FP_FINGER_STATUS_NEEDED 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.418: Processing command SLEEP 800 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.418: Sleeping 800ms 211s (process:4495): libfprint-virtual_device-DEBUG: 20:26:59.418: Sleeping now, command queued for later: SCAN bar-print 211s (process:4495): libfprint-device-DEBUG: 20:26:59.655: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.219: Sleeping completed 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.219: Processing command SCAN bar-print 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 212s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:00.219: Trying to identify print 'bar-print' against a gallery of 1 prints 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Device reported finger status change: FP_FINGER_STATUS_NEEDED 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Device reported identify completion 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Device reported finger status change: FP_FINGER_STATUS_NONE 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:00.219: Got a new connection! 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.219: Got instructions of length 5 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.219: Received command CONT 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.219: Processing command CONT 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Device reported deletion completion 212s (process:4495): libfprint-device-DEBUG: 20:27:00.219: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 212s (process:4495): libfprint-device-DEBUG: 20:27:00.220: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:00.220: Got a new connection! 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Got instructions of length 16 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Received command SET_KEEP_ALIVE 0 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Keep alive toggled: 0 212s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:00.220: Got a new connection! 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Got instructions of length 19 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Received command SET_ENROLL_STAGES 5 212s (process:4495): libfprint-device-DEBUG: 20:27:00.220: Device reported close completion 212s (process:4495): libfprint-device-DEBUG: 20:27:00.220: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 212s (process:4495): libfprint-device-DEBUG: 20:27:00.220: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s Enroll done 212s ok 212s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: 180016180: ../libfprint/drivers/virtual-device.c:387 212s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:00.220: 180016191: ../libfprint/drivers/virtual-device-listener.c:153 212s (process:4495): libfprint-device-DEBUG: 20:27:00.220: Device reported open completion 212s (process:4495): libfprint-device-DEBUG: 20:27:00.220: Completing action FPI_DEVICE_ACTION_OPEN in idle! 212s (process:4495): libfprint-device-DEBUG: 20:27:00.220: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:00.220: Got a new connection! 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Got instructions of length 26 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Received command SET_CANCELLATION_ENABLED 0 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.220: Cancellation support toggled: 0 212s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:00.220: Got a new connection! 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.221: Got instructions of length 10 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.221: Received command SLEEP 1500 212s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:00.221: Got a new connection! 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.221: Got instructions of length 14 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.221: Received command SCAN foo-print 212s (process:4495): libfprint-device-DEBUG: 20:27:00.221: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.221: Processing command SLEEP 1500 212s (process:4495): libfprint-virtual_device-DEBUG: 20:27:00.221: Sleeping 1500ms 212s (process:4495): libfprint-device-DEBUG: 20:27:00.521: Idle cancelling on ongoing operation! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.722: Sleeping completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Device reported identify completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.722: Processing command SCAN foo-print 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.722: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: 181518674: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.723: 181518698: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.723: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: Received command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.723: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.723: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.723: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.724: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.724: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.724: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.724: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Print for finger FP_FINGER_LEFT_LITTLE enrolled 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.724: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.725: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Received command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.725: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.725: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Keep alive toggled: 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.725: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: Received command SET_ENROLL_STAGES 5 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s Enroll done 213s ok 213s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.725: 181521540: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.725: 181521546: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.725: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.726: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Received command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.726: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.726: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.726: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.726: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.726: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.727: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Print for finger FP_FINGER_LEFT_LITTLE enrolled 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.727: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.727: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.727: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.727: Keep alive toggled: 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.727: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Received command SET_ENROLL_STAGES 5 213s (process:4495): libfprint-device-DEBUG: 20:27:01.728: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.728: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.728: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: 181523866: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.728: 181523888: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.728: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.728: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.728: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.728: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Received command SET_ENROLL_STAGES 8 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.728: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.728: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.728: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.729: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Received command RETRY 1 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.729: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.729: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Received command RETRY 3 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.729: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.729: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Received command RETRY 2 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.729: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.729: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.729: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Got instructions of length 8 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Received command SLEEP 10 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.730: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Got instructions of length 8 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Received command SLEEP 20 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.730: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Received command RETRY 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.730: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Received command RETRY 3 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.730: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.730: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Got instructions of length 15 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Received command SCAN another-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.730: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.730: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.731: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Received command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 1 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 2 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command RETRY 1 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 2 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 3 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command RETRY 3 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 3 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 4 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command RETRY 2 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 4 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.731: Device reported enroll progress, reported 5 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Processing command SLEEP 10 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.731: Sleeping 10ms 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.741: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.741: Processing command SLEEP 20 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.741: Sleeping 20ms 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Processing command RETRY 0 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported enroll progress, reported 5 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Processing command RETRY 3 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported enroll progress, reported 5 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported enroll progress, reported 6 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Processing command SCAN another-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported enroll progress, reported 6 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported enroll progress, reported 7 of 8 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.761: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.761: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Device reported enroll progress, reported 8 of 8 have been completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Print for finger FP_FINGER_UNKNOWN enrolled 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.762: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.762: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Keep alive toggled: 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.762: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Received command SET_ENROLL_STAGES 5 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: 181558371: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.762: 181558377: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.762: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.762: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Got instructions of length 8 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.762: Received command SLEEP 50 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command RETRY 1 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 8 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command SLEEP 50 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command SCAN print-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command RETRY 2 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.763: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Got instructions of length 15 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.763: Received command SCAN another-id 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.764: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.764: Got instructions of length 13 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.764: Received command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.764: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.764: Processing command SLEEP 50 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.764: Sleeping 50ms 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Processing command RETRY 1 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.814: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Processing command SLEEP 50 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.814: Sleeping 50ms 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.864: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Processing command RETRY 2 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Processing command SCAN another-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Sleeping completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Processing command SCAN print-id 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Print for finger FP_FINGER_UNKNOWN enrolled 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.865: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.865: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.865: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.866: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: Keep alive toggled: 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.866: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: Received command SET_ENROLL_STAGES 5 213s (process:4495): libfprint-device-DEBUG: 20:27:01.866: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.866: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.866: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s ok 213s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: 181662167: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.866: 181662192: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.866: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.866: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.866: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.866: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.866: Received command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.866: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.867: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.867: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.867: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.867: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.867: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.868: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Print for finger FP_FINGER_LEFT_RING enrolled 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.868: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Received command ERROR 0 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Processing command ERROR 0 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported identify completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.868: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.868: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.868: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.869: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Keep alive toggled: 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.869: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Received command SET_ENROLL_STAGES 5 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: 181665240: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.869: 181665262: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.869: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.869: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.869: Received command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.870: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.870: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.870: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.870: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.870: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.871: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Print for finger FP_FINGER_LEFT_THUMB enrolled 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.871: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Received command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:01.871: Trying to identify print 'testprint' against a gallery of 1 prints 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported identify result 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported identify completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.871: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.871: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Keep alive toggled: 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.871: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: Received command SET_ENROLL_STAGES 5 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.871: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.871: 181667572: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.871: 181667578: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.872: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Received command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported enroll progress, reported 1 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.872: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported enroll progress, reported 2 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.872: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported enroll progress, reported 3 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.872: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported enroll progress, reported 4 of 5 have been completed 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Sleeping completed 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.872: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Got instructions of length 14 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Received command SCAN testprint 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.872: Processing command SCAN testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported enroll progress, reported 5 of 5 have been completed 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported enroll completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Print for finger FP_FINGER_LEFT_RING enrolled 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.872: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.873: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Got instructions of length 18 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Received command SCAN not-testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Processing command SCAN not-testprint 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 213s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:01.873: Trying to identify print 'not-testprint' against a gallery of 1 prints 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported identify result 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported identify completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.873: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.873: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Keep alive toggled: 0 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.873: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Got instructions of length 19 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: Received command SET_ENROLL_STAGES 5 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported close completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s Enroll done 213s ok 213s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.873: 181669504: ../libfprint/drivers/virtual-device.c:387 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.873: 181669532: ../libfprint/drivers/virtual-device-listener.c:153 213s (process:4495): libfprint-device-DEBUG: 20:27:01.873: Device reported open completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Completing action FPI_DEVICE_ACTION_OPEN in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.874: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Got instructions of length 7 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Received command RETRY 1 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Processing command RETRY 1 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Virtual device scan failed with error: The swipe was too short, please try again. 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Device reported verify result 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Device reported verify completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Device reported finger status change: FP_FINGER_STATUS_NONE 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.874: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Got instructions of length 5 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Received command CONT 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Processing command CONT 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Device reported deletion completion 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 213s (process:4495): libfprint-device-DEBUG: 20:27:01.874: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 213s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.874: Got a new connection! 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Got instructions of length 16 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Received command SET_KEEP_ALIVE 0 213s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.874: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.875: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.875: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.875: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.875: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s ok 214s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: 181670961: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.875: 181670979: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.875: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.875: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.875: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.875: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: Received command SET_ENROLL_STAGES 8 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.875: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: Received command SCAN print-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.875: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.875: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Received command SCAN print-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.876: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Received command RETRY 1 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.876: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Received command SCAN print-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.876: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Received command RETRY 3 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.876: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Received command SCAN print-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.876: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Received command RETRY 2 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.876: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.876: Received command SCAN print-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.877: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Received command SLEEP 10 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.877: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Received command SLEEP 20 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.877: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Received command RETRY 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.877: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Received command RETRY 3 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.877: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Received command SCAN print-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.877: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.877: Received command SCAN another-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.878: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Received command SCAN print-id 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.878: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Received command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 1 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 2 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command RETRY 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 2 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 3 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command RETRY 3 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 3 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 4 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command RETRY 2 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 4 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.878: Device reported enroll progress, reported 5 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Processing command SLEEP 10 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.878: Sleeping 10ms 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.889: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.889: Processing command SLEEP 20 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.889: Sleeping 20ms 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Processing command RETRY 0 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported enroll progress, reported 5 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Processing command RETRY 3 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported enroll progress, reported 5 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported enroll progress, reported 6 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Processing command SCAN another-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported enroll progress, reported 6 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported enroll progress, reported 7 of 8 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.909: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported enroll progress, reported 8 of 8 have been completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported enroll completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Print for finger FP_FINGER_UNKNOWN enrolled 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.909: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.909: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Received command RETRY 2 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Processing command RETRY 2 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Virtual device scan failed with error: The finger was not centered properly, please try again. 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Device reported verify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Device reported verify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.910: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Received command SLEEP 50 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.910: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Received command RETRY 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Processing command SLEEP 50 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.910: Sleeping 50ms 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.960: Sleeping completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.960: Processing command RETRY 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.960: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.960: Virtual device scan failed with error: The swipe was too short, please try again. 214s (process:4495): libfprint-device-DEBUG: 20:27:01.960: Device reported verify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.960: Device reported verify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.960: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.961: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Received command SCAN another-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Processing command SCAN another-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Virtual device scanned print another-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported verify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported verify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.961: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Got instructions of length 13 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Received command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Processing command SCAN print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.961: Virtual device scanned print print-id 214s (process:4495): libfprint-device-DEBUG: 20:27:01.961: Device reported verify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Device reported verify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.962: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.962: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.962: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.962: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s ok 214s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: 181758611: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.963: 181758635: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.963: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Received command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported enroll progress, reported 1 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.963: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.963: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.963: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.964: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Received command RETRY 1 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Processing command RETRY 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.964: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported enroll progress, reported 3 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.964: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported enroll progress, reported 4 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.964: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported enroll progress, reported 5 of 5 have been completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported enroll completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Print for finger FP_FINGER_LEFT_LITTLE enrolled 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.964: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.964: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.964: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.965: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.965: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s Enroll done 214s ok 214s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: 181760977: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.965: 181760983: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.965: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Received command FINGER 1 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.965: Processing command FINGER 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.965: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Received command FINGER 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Processing command FINGER 0 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Idle cancelling on ongoing operation! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Got cancellation! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.966: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.966: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.966: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.966: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.966: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.967: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.967: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s ok 214s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.967: 181762744: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.967: 181762766: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.967: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.967: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.967: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.967: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.967: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.967: Received command SLEEP 10 214s (process:4495): libfprint-device-DEBUG: 20:27:01.967: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.967: Processing command SLEEP 10 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.967: Sleeping 10ms 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.977: Sleeping completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.977: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.977: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.977: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.977: Received command FINGER 1 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.977: Processing command FINGER 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.977: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.978: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Got instructions of length 8 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Received command FINGER 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Processing command FINGER 0 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Idle cancelling on ongoing operation! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Got cancellation! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.978: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.978: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.978: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.978: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.978: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s ok 214s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: 181774809: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.979: 181774831: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.979: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: Received command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported enroll progress, reported 1 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.979: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.979: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.979: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.980: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported enroll progress, reported 3 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.980: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported enroll progress, reported 4 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.980: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported enroll progress, reported 5 of 5 have been completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported enroll completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Print for finger FP_FINGER_RIGHT_THUMB enrolled 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.980: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Received command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported enroll progress, reported 1 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.980: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.980: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.980: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.981: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported enroll progress, reported 3 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.981: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported enroll progress, reported 4 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.981: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported enroll progress, reported 5 of 5 have been completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported enroll completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Print for finger FP_FINGER_LEFT_THUMB enrolled 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.981: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Received command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.981: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:01.981: Trying to identify print 'right-thumb' against a gallery of 2 prints 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported identify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.981: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.982: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Received command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:01.982: Trying to identify print 'left-thumb' against a gallery of 2 prints 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Device reported identify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.982: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.982: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.982: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.982: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s Enroll done 214s Enroll done 214s ok 214s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: 181778860: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.983: 181778882: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.983: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: Got instructions of length 23 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: Received command SCAN not-existing-print 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: Processing command SCAN not-existing-print 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:01.983: Trying to identify print 'not-existing-print' against a gallery of 1 prints 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported identify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.983: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.983: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.984: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.984: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s ok 214s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: 181780267: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.984: 181780286: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.984: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.984: Received command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported enroll progress, reported 1 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.985: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.985: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported enroll progress, reported 3 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.985: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.985: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.985: Device reported enroll progress, reported 4 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.986: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Received command SCAN right-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported enroll progress, reported 5 of 5 have been completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported enroll completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Print for finger FP_FINGER_RIGHT_THUMB enrolled 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.986: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Received command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported enroll progress, reported 1 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.986: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.986: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported enroll progress, reported 3 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.986: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.986: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.986: Device reported enroll progress, reported 4 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.987: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Received command SCAN left-thumb 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported enroll progress, reported 5 of 5 have been completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported enroll completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Print for finger FP_FINGER_LEFT_THUMB enrolled 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.987: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Received command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Processing command SCAN right-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:01.987: Trying to identify print 'right-thumb' against a gallery of 1 prints 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported identify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.987: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Got instructions of length 15 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Received command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.987: Processing command SCAN left-thumb 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:01.987: Trying to identify print 'left-thumb' against a gallery of 1 prints 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported identify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.987: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.988: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.988: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.988: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s Enroll done 214s Enroll done 214s ok 214s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.988: 181784375: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.988: 181784403: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.988: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.989: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Got instructions of length 7 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Received command RETRY 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Processing command RETRY 1 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Device reported identify result 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Device reported identify completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.989: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.989: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.989: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.989: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.989: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s ok 214s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: 181785847: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.990: 181785870: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s skipped 'Device supports identification' 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.990: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: Got instructions of length 5 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: Received command CONT 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: Processing command CONT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Device reported deletion completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.990: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.990: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: Got instructions of length 16 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: Received command SET_KEEP_ALIVE 0 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.990: Keep alive toggled: 0 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.991: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Got instructions of length 19 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Received command SET_ENROLL_STAGES 5 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Device reported close completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: 181786898: ../libfprint/drivers/virtual-device.c:387 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.991: 181786916: ../libfprint/drivers/virtual-device-listener.c:153 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Device reported open completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Completing action FPI_DEVICE_ACTION_OPEN in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.991: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Received command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Device reported enroll progress, reported 1 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.991: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.991: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.991: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported enroll progress, reported 2 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.992: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported enroll progress, reported 3 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.992: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported enroll progress, reported 4 of 5 have been completed 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Sleeping completed 214s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:01.992: Got a new connection! 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Got instructions of length 14 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Received command SCAN testprint 214s (process:4495): libfprint-virtual_device-DEBUG: 20:27:01.992: Processing command SCAN testprint 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NEEDED 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported enroll progress, reported 5 of 5 have been completed 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported enroll completion 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Device reported finger status change: FP_FINGER_STATUS_NONE 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Print for finger FP_FINGER_RIGHT_THUMB enrolled 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:01.992: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 214s Executing: libfprint-2/virtual-device.test 214s (process:4495): libfprint-device-DEBUG: 20:27:02.493: Device reported listing completion 214s (process:4495): libfprint-device-DEBUG: 20:27:02.493: Completing action FPI_DEVICE_ACTION_LIST in idle! 214s (process:4495): libfprint-device-DEBUG: 20:27:02.493: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:02.994: Deleting print testprint for user testuser 215s (process:4495): libfprint-device-DEBUG: 20:27:02.994: Device reported deletion completion 215s (process:4495): libfprint-device-DEBUG: 20:27:02.994: Completing action FPI_DEVICE_ACTION_DELETE in idle! 215s (process:4495): libfprint-device-DEBUG: 20:27:02.994: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:4495): libfprint-device-DEBUG: 20:27:03.495: Device reported listing completion 215s (process:4495): libfprint-device-DEBUG: 20:27:03.495: Completing action FPI_DEVICE_ACTION_LIST in idle! 215s (process:4495): libfprint-device-DEBUG: 20:27:03.495: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.495: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.495: Got instructions of length 5 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.495: Received command CONT 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.495: Processing command CONT 215s (process:4495): libfprint-device-DEBUG: 20:27:03.495: Device reported deletion completion 215s (process:4495): libfprint-device-DEBUG: 20:27:03.495: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 215s (process:4495): libfprint-device-DEBUG: 20:27:03.495: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.495: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.495: Got instructions of length 16 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.495: Received command SET_KEEP_ALIVE 0 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.495: Keep alive toggled: 0 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.496: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Got instructions of length 19 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Received command SET_ENROLL_STAGES 5 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported close completion 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s Enroll done 215s 215s blub 'testprint' 215s ok 215s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: 183291889: ../libfprint/drivers/virtual-device.c:387 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.496: 183291902: ../libfprint/drivers/virtual-device-listener.c:153 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported open completion 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Completing action FPI_DEVICE_ACTION_OPEN in idle! 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.496: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Got instructions of length 14 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Received command SCAN testprint 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Processing command SCAN testprint 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported enroll progress, reported 1 of 5 have been completed 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Sleeping completed 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.496: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Got instructions of length 14 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Received command SCAN testprint 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Processing command SCAN testprint 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:4495): libfprint-device-DEBUG: 20:27:03.496: Device reported enroll progress, reported 2 of 5 have been completed 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.496: Sleeping completed 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.496: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Got instructions of length 14 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Received command SCAN testprint 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Processing command SCAN testprint 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported enroll progress, reported 3 of 5 have been completed 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Sleeping completed 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.497: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Got instructions of length 14 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Received command SCAN testprint 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Processing command SCAN testprint 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported enroll progress, reported 4 of 5 have been completed 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Sleeping completed 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.497: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Got instructions of length 14 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Received command SCAN testprint 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Processing command SCAN testprint 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported enroll progress, reported 5 of 5 have been completed 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported enroll completion 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Device reported finger status change: FP_FINGER_STATUS_NONE 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Print for finger FP_FINGER_RIGHT_THUMB enrolled 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 215s (process:4495): libfprint-device-DEBUG: 20:27:03.497: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 215s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.497: Got a new connection! 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Got instructions of length 16 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Received command REMOVE testprint 215s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.497: Processing command REMOVE testprint 216s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:03.998: Deleting print testprint for user testuser 216s (process:4495): libfprint-device-DEBUG: 20:27:03.998: Device reported deletion completion 216s (process:4495): libfprint-device-DEBUG: 20:27:03.998: Completing action FPI_DEVICE_ACTION_DELETE in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:03.998: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.998: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.998: Got instructions of length 5 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.998: Received command CONT 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.998: Processing command CONT 216s (process:4495): libfprint-device-DEBUG: 20:27:03.998: Device reported deletion completion 216s (process:4495): libfprint-device-DEBUG: 20:27:03.998: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:03.998: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.998: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.998: Got instructions of length 16 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.998: Received command SET_KEEP_ALIVE 0 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.998: Keep alive toggled: 0 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.999: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.999: Got instructions of length 19 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.999: Received command SET_ENROLL_STAGES 5 216s (process:4495): libfprint-device-DEBUG: 20:27:03.999: Device reported close completion 216s (process:4495): libfprint-device-DEBUG: 20:27:03.999: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:03.999: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s Enroll done 216s ok 216s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:03.999: 183794837: ../libfprint/drivers/virtual-device.c:387 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:03.999: 183794845: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:4495): libfprint-device-DEBUG: 20:27:03.999: Device reported open completion 216s (process:4495): libfprint-device-DEBUG: 20:27:03.999: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:03.999: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-device-DEBUG: 20:27:04.499: Device reported listing completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.500: Completing action FPI_DEVICE_ACTION_LIST in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.500: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.500: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.500: Got instructions of length 5 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.500: Received command CONT 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.500: Processing command CONT 216s (process:4495): libfprint-device-DEBUG: 20:27:04.500: Device reported deletion completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.500: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.500: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.500: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.500: Got instructions of length 16 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.501: Received command SET_KEEP_ALIVE 0 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.501: Keep alive toggled: 0 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.501: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.501: Got instructions of length 19 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.501: Received command SET_ENROLL_STAGES 5 216s (process:4495): libfprint-device-DEBUG: 20:27:04.501: Device reported close completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.501: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.501: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s ok 216s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.501: 184297590: ../libfprint/drivers/virtual-device.c:387 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.502: 184297634: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:4495): libfprint-device-DEBUG: 20:27:04.502: Device reported open completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.502: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.502: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.502: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.502: Got instructions of length 9 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.502: Received command SLEEP 100 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.502: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.502: Got instructions of length 7 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.502: Received command ERROR 4 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.503: Processing command SLEEP 100 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.503: Sleeping 100ms 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.603: Sleeping completed 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.603: Processing command ERROR 4 216s (process:4495): libfprint-device-DEBUG: 20:27:04.603: Device reported listing completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.603: Completing action FPI_DEVICE_ACTION_LIST in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.603: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.603: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.603: Got instructions of length 5 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.603: Received command CONT 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.603: Processing command CONT 216s (process:4495): libfprint-device-DEBUG: 20:27:04.603: Device reported deletion completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.603: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.604: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.604: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: Got instructions of length 16 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: Received command SET_KEEP_ALIVE 0 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: Keep alive toggled: 0 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.604: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: Got instructions of length 19 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: Received command SET_ENROLL_STAGES 5 216s (process:4495): libfprint-device-DEBUG: 20:27:04.604: Device reported close completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.604: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.604: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s ok 216s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: 184400267: ../libfprint/drivers/virtual-device.c:387 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.604: 184400296: ../libfprint/drivers/virtual-device-listener.c:153 216s (process:4495): libfprint-device-DEBUG: 20:27:04.604: Device reported open completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.604: Completing action FPI_DEVICE_ACTION_OPEN in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.604: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.604: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: Got instructions of length 9 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.604: Received command INSERT p1 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.605: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Got instructions of length 7 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Received command SCAN p2 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Processing command INSERT p1 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Processing command SCAN p2 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported enroll progress, reported 1 of 5 have been completed 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Sleeping completed 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.605: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Got instructions of length 7 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Received command SCAN p2 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Processing command SCAN p2 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported enroll progress, reported 2 of 5 have been completed 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Sleeping completed 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.605: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Got instructions of length 7 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Received command SCAN p2 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Processing command SCAN p2 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:4495): libfprint-device-DEBUG: 20:27:04.605: Device reported enroll progress, reported 3 of 5 have been completed 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.605: Sleeping completed 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.606: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.606: Got instructions of length 7 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.606: Received command SCAN p2 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.606: Processing command SCAN p2 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported enroll progress, reported 4 of 5 have been completed 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.606: Sleeping completed 216s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:04.606: Got a new connection! 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.606: Got instructions of length 7 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.606: Received command SCAN p2 216s (process:4495): libfprint-virtual_device-DEBUG: 20:27:04.606: Processing command SCAN p2 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported enroll progress, reported 5 of 5 have been completed 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported enroll completion 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Device reported finger status change: FP_FINGER_STATUS_NONE 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Print for finger FP_FINGER_LEFT_LITTLE enrolled 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 216s (process:4495): libfprint-device-DEBUG: 20:27:04.606: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-device-DEBUG: 20:27:05.107: Device reported listing completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.107: Completing action FPI_DEVICE_ACTION_LIST in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.107: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.107: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.107: Got instructions of length 5 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.107: Received command CONT 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.107: Processing command CONT 217s (process:4495): libfprint-device-DEBUG: 20:27:05.107: Device reported deletion completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.107: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.107: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.107: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.107: Got instructions of length 16 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.107: Received command SET_KEEP_ALIVE 0 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.107: Keep alive toggled: 0 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.107: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.107: Got instructions of length 19 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.108: Received command SET_ENROLL_STAGES 5 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Device reported close completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s Enroll done 217s ok 217s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.108: 184903854: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.108: 184903874: ../libfprint/drivers/virtual-device-listener.c:153 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.108: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.108: Got instructions of length 16 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.108: Received command IGNORED_COMMAND 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.108: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.108: Got instructions of length 7 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.108: Received command ERROR 5 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.108: Processing command IGNORED_COMMAND 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Device reported close completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.108: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: 184904662: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: Processing command ERROR 5 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s ok 217s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: 184904884: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.109: 184904929: ../libfprint/drivers/virtual-device-listener.c:153 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.109: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: Got instructions of length 16 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: Received command SET_KEEP_ALIVE 1 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: Keep alive toggled: 1 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Device reported close completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.109: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: Got instructions of length 7 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: Received command ERROR 5 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: 184905557: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.109: Processing command ERROR 5 217s (process:4495): libfprint-device-DEBUG: 20:27:05.109: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s ok 217s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.110: 184905730: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.110: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.110: Got instructions of length 19 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.110: Received command SET_ENROLL_STAGES 1 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.110: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.110: Got instructions of length 14 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.110: Received command SCAN testprint 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.110: Processing command SCAN testprint 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Device reported enroll progress, reported 1 of 1 have been completed 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Device reported enroll completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Print for finger FP_FINGER_LEFT_LITTLE enrolled 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.110: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.110: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Got instructions of length 5 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Received command CONT 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Processing command CONT 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Device reported deletion completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.111: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Got instructions of length 16 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Received command SET_KEEP_ALIVE 0 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Keep alive toggled: 0 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.111: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Got instructions of length 19 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Received command SET_ENROLL_STAGES 5 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Device reported close completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s Enroll done 217s ok 217s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: 184907307: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.111: 184907328: ../libfprint/drivers/virtual-device-listener.c:153 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.111: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.111: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.111: Got instructions of length 23 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Received command SCAN not-existing-print 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Processing command SCAN not-existing-print 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Virtual device scanned print not-existing-print 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported verify result 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported verify completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.112: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Got instructions of length 5 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Received command CONT 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Processing command CONT 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported deletion completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.112: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Got instructions of length 16 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Received command SET_KEEP_ALIVE 0 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Keep alive toggled: 0 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.112: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Got instructions of length 19 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.112: Received command SET_ENROLL_STAGES 5 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Device reported close completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.112: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.113: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s ok 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.113: 184908815: ../libfprint/drivers/virtual-device.c:752 217s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:4495): libfprint-context-DEBUG: 20:27:05.113: Initializing FpContext (libfprint version 1.94.8+tod1) 217s (process:4495): libfprint-tod-DEBUG: 20:27:05.113: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 217s (process:4495): libfprint-context-DEBUG: 20:27:05.113: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-7fhw6sq9/virtual-device.socket 217s (process:4495): libfprint-context-DEBUG: 20:27:05.113: created 217s (process:4495): libfprint-context-DEBUG: 20:27:05.113: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-39lvlzp_/virtual-device-storage.socket 217s (process:4495): libfprint-context-DEBUG: 20:27:05.113: created 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Device reported probe completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Device reported probe completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Completing action FPI_DEVICE_ACTION_PROBE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Completing action FPI_DEVICE_ACTION_PROBE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.114: 184909713: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.114: 184909722: ../libfprint/drivers/virtual-device-listener.c:153 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.114: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.114: Got instructions of length 7 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.114: Received command UNPLUG 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Device reported close completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.114: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.114: 184910255: ../libfprint/drivers/virtual-device.c:752 217s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:05.114: 184910271: ../libfprint/drivers/virtual-device-storage.c:253 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.114: 184910276: ../libfprint/drivers/virtual-device.c:752 217s ok 217s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:4495): libfprint-context-DEBUG: 20:27:05.114: Initializing FpContext (libfprint version 1.94.8+tod1) 217s (process:4495): libfprint-tod-DEBUG: 20:27:05.114: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 217s (process:4495): libfprint-context-DEBUG: 20:27:05.115: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-7fhw6sq9/virtual-device.socket 217s (process:4495): libfprint-context-DEBUG: 20:27:05.115: created 217s (process:4495): libfprint-context-DEBUG: 20:27:05.115: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-39lvlzp_/virtual-device-storage.socket 217s (process:4495): libfprint-context-DEBUG: 20:27:05.115: created 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Device reported probe completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Device reported probe completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Completing action FPI_DEVICE_ACTION_PROBE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Completing action FPI_DEVICE_ACTION_PROBE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.115: 184910900: ../libfprint/drivers/virtual-device.c:387 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.115: 184910909: ../libfprint/drivers/virtual-device-listener.c:153 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Device reported open completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4495): libfprint-device-DEBUG: 20:27:05.115: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:4495): libfprint-virtual_device_connection-DEBUG: 20:27:05.115: Got a new connection! 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.115: Got instructions of length 7 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.115: Received command UNPLUG 217s (process:4495): libfprint-device-DEBUG: 20:27:05.215: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Device reported verify completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Device reported finger status change: FP_FINGER_STATUS_NONE 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Device reported close completion 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 217s (process:4495): libfprint-device-DEBUG: 20:27:05.616: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.616: 185412198: ../libfprint/drivers/virtual-device.c:752 217s (process:4495): libfprint-virtual_device_storage-DEBUG: 20:27:05.616: 185412221: ../libfprint/drivers/virtual-device-storage.c:253 217s (process:4495): libfprint-virtual_device-DEBUG: 20:27:05.616: 185412227: ../libfprint/drivers/virtual-device.c:752 217s ok 217s 217s ---------------------------------------------------------------------- 217s Ran 86 tests in 17.521s 217s 217s OK (skipped=1) 217s PASS: libfprint-2/virtual-device.test 217s Running test: libfprint-2/driver-elan.test 217s ** (umockdev-run:4513): DEBUG: 20:27:05.665: umockdev.vala:127: Created udev test bed /tmp/umockdev.6XXE22 217s ** (umockdev-run:4513): DEBUG: 20:27:05.665: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 217s ** (umockdev-run:4513): DEBUG: 20:27:05.666: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 217s ** (umockdev-run:4513): DEBUG: 20:27:05.669: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.6XXE22/dev/bus/usb/001/094 217s ** (umockdev-run:4513): DEBUG: 20:27:05.669: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 217s ** (umockdev-run:4513): DEBUG: 20:27:05.670: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 217s ** (umockdev-run:4513): DEBUG: 20:27:05.672: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.6XXE22/dev/bus/usb/001/083 217s ** (umockdev-run:4513): DEBUG: 20:27:05.673: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 217s ** (umockdev-run:4513): DEBUG: 20:27:05.673: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 217s ** (umockdev-run:4513): DEBUG: 20:27:05.676: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.6XXE22/dev/bus/usb/001/001 217s ** (umockdev-run:4513): DEBUG: 20:27:05.676: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 217s ** (umockdev-run:4513): DEBUG: 20:27:05.676: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 217s (umockdev-run:4513): GLib-GIO-DEBUG: 20:27:05.679: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 217s (process:4517): libfprint-context-DEBUG: 20:27:05.755: Initializing FpContext (libfprint version 1.94.8+tod1) 217s (process:4517): libfprint-tod-DEBUG: 20:27:05.755: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 217s (process:4517): libfprint-context-DEBUG: 20:27:05.758: No driver found for USB device 17EF:1018 217s (process:4517): libfprint-context-DEBUG: 20:27:05.758: No driver found for USB device 1D6B:0002 217s (process:4517): libfprint-device-DEBUG: 20:27:05.758: Device reported probe completion 217s (process:4517): libfprint-device-DEBUG: 20:27:05.758: Completing action FPI_DEVICE_ACTION_PROBE in idle! 217s (process:4517): libfprint-device-DEBUG: 20:27:05.758: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.759: 185555229: ../libfprint/drivers/elan.c:908 217s (process:4517): libfprint-image_device-DEBUG: 20:27:05.759: Image device open completed 217s (process:4517): libfprint-device-DEBUG: 20:27:05.759: Device reported open completion 217s (process:4517): libfprint-device-DEBUG: 20:27:05.759: Completing action FPI_DEVICE_ACTION_OPEN in idle! 217s (process:4517): libfprint-device-DEBUG: 20:27:05.759: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4517): libfprint-device-DEBUG: 20:27:05.760: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 217s (process:4517): libfprint-image_device-DEBUG: 20:27:05.760: Activating image device 217s (process:4517): libfprint-image_device-DEBUG: 20:27:05.760: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185555727: ../libfprint/drivers/elan.c:960 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185555731: ../libfprint/drivers/elan.c:951 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185555733: ../libfprint/drivers/elan.c:892 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185555736: ../libfprint/drivers/elan.c:100 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.760: [elan] ACTIVATE_NUM_STATES entering state 0 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185555750: ../libfprint/drivers/elan.c:820 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185556198: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185556213: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.760: 185556216: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: 185556653: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: 185556697: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.761: [elan] ACTIVATE_NUM_STATES entering state 1 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: 185556707: ../libfprint/drivers/elan.c:820 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: FW ver 0x0140 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.761: [elan] ACTIVATE_NUM_STATES entering state 2 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: 185556723: ../libfprint/drivers/elan.c:820 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: 185557198: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: 185557212: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.761: 185557214: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557611: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557621: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.762: [elan] ACTIVATE_NUM_STATES entering state 3 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557627: ../libfprint/drivers/elan.c:820 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: sensor dimensions, WxH: 144x64 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.762: [elan] ACTIVATE_NUM_STATES entering state 4 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557635: ../libfprint/drivers/elan.c:820 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557641: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.762: [elan] ACTIVATE_NUM_STATES completed successfully 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557647: ../libfprint/drivers/elan.c:881 217s (process:4517): libfprint-image_device-DEBUG: 20:27:05.762: Image device activation completed 217s (process:4517): libfprint-image_device-DEBUG: 20:27:05.762: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557659: ../libfprint/drivers/elan.c:960 217s (process:4517): libfprint-image_device-DEBUG: 20:27:05.762: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557669: ../libfprint/drivers/elan.c:960 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557671: ../libfprint/drivers/elan.c:792 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557673: ../libfprint/drivers/elan.c:100 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.762: [elan] CALIBRATE_NUM_STATES entering state 0 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185557679: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-device-DEBUG: 20:27:05.762: Device reported finger status change: FP_FINGER_STATUS_NEEDED 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185558096: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185558110: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185558112: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185558586: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.762: 185558606: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.763: [elan] CALIBRATE_NUM_STATES entering state 1 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185558613: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185558615: ../libfprint/drivers/elan.c:156 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185558620: ../libfprint/drivers/elan.c:118 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.763: [elan] CALIBRATE_NUM_STATES entering state 2 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185558636: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559069: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559082: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559085: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559524: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559535: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.763: [elan] CALIBRATE_NUM_STATES entering state 3 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559541: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559544: ../libfprint/drivers/elan.c:634 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: calibration mean: 8421, bg mean: 5805, delta: 2616 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.763: [elan] CALIBRATE_NUM_STATES entering state 4 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.763: 185559557: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.764: 185559946: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.764: 185559957: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.764: 185559959: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.764: 185560406: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.764: 185560420: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.764: [elan] CALIBRATE_NUM_STATES entering state 5 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.764: 185560426: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.764: calibration status: 0x01 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.814: [elan] CALIBRATE_NUM_STATES entering state 6 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.814: 185610530: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.814: [elan] CALIBRATE_NUM_STATES entering state 4 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.814: 185610540: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.815: 185610836: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.815: 185610847: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.815: 185610850: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.815: 185611279: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.815: 185611294: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.815: [elan] CALIBRATE_NUM_STATES entering state 5 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.815: 185611300: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.815: calibration status: 0x01 217s (process:4517): libfprint-device-DEBUG: 20:27:05.859: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.865: [elan] CALIBRATE_NUM_STATES entering state 6 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.865: 185661381: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.865: [elan] CALIBRATE_NUM_STATES entering state 4 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.865: 185661389: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.866: 185661680: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.866: 185661691: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.866: 185661694: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.866: 185662088: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.866: 185662104: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.866: [elan] CALIBRATE_NUM_STATES entering state 5 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.866: 185662113: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.866: calibration status: 0x01 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.916: [elan] CALIBRATE_NUM_STATES entering state 6 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.916: 185712197: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.916: [elan] CALIBRATE_NUM_STATES entering state 4 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.916: 185712204: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.917: 185712747: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.917: 185712759: ../libfprint/drivers/elan.c:366 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.917: 185712761: ../libfprint/drivers/elan.c:379 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.917: 185713191: ../libfprint/drivers/elan.c:346 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.917: 185713205: ../libfprint/drivers/elan.c:335 217s (process:4517): libfprint-SSM-DEBUG: 20:27:05.917: [elan] CALIBRATE_NUM_STATES entering state 5 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.917: 185713211: ../libfprint/drivers/elan.c:691 217s (process:4517): libfprint-elan-DEBUG: 20:27:05.917: calibration status: 0x01 218s (process:4517): libfprint-SSM-DEBUG: 20:27:05.967: [elan] CALIBRATE_NUM_STATES entering state 6 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.967: 185763302: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-SSM-DEBUG: 20:27:05.967: [elan] CALIBRATE_NUM_STATES entering state 4 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.967: 185763308: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.968: 185763621: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.968: 185763633: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.968: 185763636: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.968: 185764032: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.968: 185764046: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:05.968: [elan] CALIBRATE_NUM_STATES entering state 5 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.968: 185764053: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:05.968: calibration status: 0x01 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.018: [elan] CALIBRATE_NUM_STATES entering state 6 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.018: 185814149: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.018: [elan] CALIBRATE_NUM_STATES entering state 4 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.018: 185814158: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.018: 185814494: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.018: 185814505: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.018: 185814508: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: 185814933: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: 185814945: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.019: [elan] CALIBRATE_NUM_STATES entering state 5 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: 185814951: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: calibration status: 0x03 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.019: [elan] CALIBRATE_NUM_STATES entering state 0 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: 185814959: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: 185815366: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: 185815380: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.019: 185815383: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185815845: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185815857: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.020: [elan] CALIBRATE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185815863: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185815865: ../libfprint/drivers/elan.c:156 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185815868: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.020: [elan] CALIBRATE_NUM_STATES entering state 2 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185815881: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185816266: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185816280: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.020: 185816283: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185816708: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185816720: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.021: [elan] CALIBRATE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185816725: ../libfprint/drivers/elan.c:691 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185816728: ../libfprint/drivers/elan.c:634 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: calibration mean: 8339, bg mean: 8146, delta: 193 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.021: [elan] CALIBRATE_NUM_STATES completed successfully 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185816746: ../libfprint/drivers/elan.c:776 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185816749: ../libfprint/drivers/elan.c:620 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185816751: ../libfprint/drivers/elan.c:100 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.021: [elan] CAPTURE_NUM_STATES entering state 0 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185817166: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185817179: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185817182: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: skipping read, not expecting anything 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.021: 185817187: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.021: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185817610: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185817622: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185817626: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185818024: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185818039: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.022: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-device-DEBUG: 20:27:06.022: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.022: Image device reported finger status: on 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185818078: ../libfprint/drivers/elan.c:960 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185818476: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185818487: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.022: 185818490: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.023: 185818917: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.023: 185818929: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.023: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.023: 185818935: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.023: 185818945: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.023: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.023: 185819357: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.023: 185819370: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.023: 185819373: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.024: 185819755: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.024: 185819765: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.024: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.024: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.024: 185820157: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.024: 185820171: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.024: 185820173: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185820616: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185820628: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.025: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185820634: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185820640: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.025: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185821065: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185821079: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185821082: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185821529: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.025: 185821540: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.025: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.025: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.026: 185821986: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.026: 185821996: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.026: 185821999: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.026: 185822489: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.026: 185822501: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.026: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.026: 185822507: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.026: 185822514: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.026: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.027: 185822897: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.027: 185822907: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.027: 185822910: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.027: 185823351: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.027: 185823365: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.027: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.027: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.028: 185823782: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.028: 185823793: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.028: 185823796: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.028: 185824228: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.028: 185824243: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.028: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.028: 185824249: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.028: 185824255: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.028: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185824707: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185824718: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185824721: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185825145: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185825159: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.029: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.029: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185825545: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185825555: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.029: 185825558: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.030: 185825974: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.030: 185825986: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.030: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.030: 185825992: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.030: 185826000: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.030: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.030: 185826476: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.030: 185826486: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.030: 185826489: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.031: 185826888: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.031: 185826900: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.031: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.031: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.031: 185827389: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.031: 185827403: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.031: 185827405: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.032: 185827840: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.032: 185827852: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.032: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.032: 185827858: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.032: 185827865: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.032: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.032: 185828347: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.032: 185828361: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.032: 185828364: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.033: 185828847: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.033: 185828858: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.033: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.033: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.033: 185829272: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.033: 185829286: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.033: 185829289: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185829722: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185829736: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.034: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185829743: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185829751: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.034: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185830201: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185830214: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185830217: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185830594: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.034: 185830605: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.035: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.035: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.035: 185830993: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.035: 185831018: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.035: 185831022: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.035: 185831470: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.035: 185831482: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.035: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.035: 185831488: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.035: 185831515: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.035: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.036: 185831967: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.036: 185831978: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.036: 185831981: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.036: 185832385: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.036: 185832399: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.036: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.036: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.037: 185832826: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.037: 185832837: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.037: 185832839: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.037: 185833271: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.037: 185833286: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.037: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.037: 185833292: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.037: 185833298: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.037: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185833687: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185833698: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185833700: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185834078: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185834093: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.038: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.038: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185834503: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185834514: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.038: 185834516: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.039: 185834929: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.039: 185834940: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.039: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.039: 185834946: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.039: 185834952: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.039: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.039: 185835408: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.039: 185835421: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.039: 185835424: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.040: 185835823: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.040: 185835834: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.040: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.040: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.040: 185836419: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.040: 185836433: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.040: 185836436: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.041: 185836896: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.041: 185836908: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.041: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.041: 185836914: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.041: 185836921: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.041: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.041: 185837311: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.041: 185837325: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.041: 185837328: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185837724: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185837734: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.042: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.042: Image device reported finger status: on 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185838064: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185838081: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185838085: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185838502: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185838514: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.042: [elan] CAPTURE_NUM_STATES entering state 3 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185838520: ../libfprint/drivers/elan.c:203 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.042: 185838526: ../libfprint/drivers/elan.c:118 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.042: [elan] CAPTURE_NUM_STATES entering state 1 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185838918: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185838928: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185838931: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185839339: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185839353: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.043: [elan] CAPTURE_NUM_STATES entering state 2 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.043: [elan] CAPTURE_NUM_STATES completed successfully 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185839364: ../libfprint/drivers/elan.c:586 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185839367: ../libfprint/drivers/elan.c:315 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.043: 185839372: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.044: 185840096: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.045: 185840831: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.045: 185841532: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.046: 185842320: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.047: 185843079: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.048: 185843784: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.048: 185844498: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.049: 185845236: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.050: 185845969: ../libfprint/drivers/elan.c:272 218s (process:4517): libfprint-assembling-DEBUG: 20:27:06.126: calc delta completed in 0.075139 secs 218s (process:4517): libfprint-assembling-DEBUG: 20:27:06.198: calc delta completed in 0.072285 secs 218s (process:4517): libfprint-assembling-DEBUG: 20:27:06.198: errors: 233151 rev: 207411 218s (process:4517): libfprint-assembling-DEBUG: 20:27:06.198: height is -185 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.198: Image device captured an image 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.199: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.199: 185994664: ../libfprint/drivers/elan.c:960 218s (process:4517): libfprint-device-DEBUG: 20:27:06.199: Device reported finger status change: FP_FINGER_STATUS_PRESENT 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.199: 185994675: ../libfprint/drivers/elan.c:507 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.199: 185994677: ../libfprint/drivers/elan.c:100 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.199: [elan] STOP_CAPTURE_NUM_STATES entering state 0 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.199: 185994685: ../libfprint/drivers/elan.c:466 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996356: ../libfprint/drivers/elan.c:346 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996370: ../libfprint/drivers/elan.c:366 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996373: ../libfprint/drivers/elan.c:379 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: skipping read, not expecting anything 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996378: ../libfprint/drivers/elan.c:335 218s (process:4517): libfprint-SSM-DEBUG: 20:27:06.200: [elan] STOP_CAPTURE_NUM_STATES completed successfully 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996384: ../libfprint/drivers/elan.c:483 218s (process:4517): libfprint-device-DEBUG: 20:27:06.200: Device reported finger status change: FP_FINGER_STATUS_NONE 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.200: Image device reported finger status: off 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.200: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996401: ../libfprint/drivers/elan.c:960 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.200: Deactivating image device 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.200: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996409: ../libfprint/drivers/elan.c:960 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996412: ../libfprint/drivers/elan.c:975 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.200: Image device deactivation completed 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.200: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.200: 185996422: ../libfprint/drivers/elan.c:960 218s (process:4517): libfprint-image-DEBUG: 20:27:06.209: Minutiae scan completed in 0.010063 secs 218s (process:4517): libfprint-device-DEBUG: 20:27:06.209: Device reported capture completion 218s (process:4517): libfprint-device-DEBUG: 20:27:06.209: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 218s (process:4517): libfprint-device-DEBUG: 20:27:06.209: Updated temperature model after 0.35 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.209: 186004989: ../libfprint/drivers/elan.c:939 218s (process:4517): libfprint-elan-DEBUG: 20:27:06.209: 186004995: ../libfprint/drivers/elan.c:100 218s (process:4517): libfprint-image_device-DEBUG: 20:27:06.209: Image device close completed 218s (process:4517): libfprint-device-DEBUG: 20:27:06.209: Device reported close completion 218s (process:4517): libfprint-device-DEBUG: 20:27:06.209: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 218s (process:4517): libfprint-device-DEBUG: 20:27:06.209: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 218s ** (umockdev-run:4513): DEBUG: 20:27:06.273: umockdev.vala:154: Removing test bed /tmp/umockdev.6XXE22 218s (umockdev-run:4513): GLib-DEBUG: 20:27:06.279: unsetenv() is not thread-safe and should not be used after threads are created 218s Comparing PNGs /tmp/libfprint-umockdev-test-h7z8_wb0/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 218s PASS: libfprint-2/driver-elan.test 218s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.3.test 218s TAP version 14 218s # random seed: R02S3f0193f42d7615de556a87ba72c77cb7 218s 1..4 218s # Start of context tests 218s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 218s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 218s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7414bcd1c987, GType is 104177789996432 218s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 218s # libfprint-tod-DEBUG: Initializing features for driver ssm_test_dev_tod_v1+1.90.3 218s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 218s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7414bcd1653b, GType is 104177790001232 218s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 218s # libfprint-tod-DEBUG: Initializing features for driver fake_test_dev_tod_v1+1.90.3 218s ok 1 /context/new 218s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 218s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 218s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 218s ok 2 /context/no-devices 218s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 218s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 218s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7414bcd1c987, GType is 104177789996432 218s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 218s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 218s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7414bcd1653b, GType is 104177790001232 218s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 218s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 218s # libfprint-context-DEBUG: created 218s # libfprint-device-DEBUG: Device reported probe completion 218s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 218s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 218s # libfprint-device-DEBUG: Device reported open completion 218s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 218s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 218s # libfprint-device-DEBUG: Device reported close completion 218s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 218s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 218s ok 3 /context/has-virtual-device 218s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.8+tod1) 218s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-ssm-test-v1+1.90.3-x86_64.so 218s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7414bcd1c987, GType is 104177789996432 218s # libfprint-tod-DEBUG: Loading driver ssm_test_dev_tod_v1+1.90.3 (Virtual device for SSM Testing) 218s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/tod-x86_64-v1+1.90.3/libdevice-fake-tod-test-driver-v1+1.90.3-x86_64.so 218s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x7414bcd1653b, GType is 104177790001232 218s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_v1+1.90.3 (Virtual device for debugging) 218s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 218s # libfprint-context-DEBUG: created 218s # libfprint-device-DEBUG: Device reported probe completion 218s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 218s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 218s ok 4 /context/enumerates-new-devices 218s # End of context tests 218s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_v1+1.90.3.test 218s Running test: libfprint-2/driver-synaptics.test 218s ** (umockdev-run:4538): DEBUG: 20:27:06.341: umockdev.vala:127: Created udev test bed /tmp/umockdev.BNT712 218s ** (umockdev-run:4538): DEBUG: 20:27:06.341: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 218s ** (umockdev-run:4538): DEBUG: 20:27:06.342: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 218s ** (umockdev-run:4538): DEBUG: 20:27:06.345: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.BNT712/dev/bus/usb/001/004 218s ** (umockdev-run:4538): DEBUG: 20:27:06.345: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 218s ** (umockdev-run:4538): DEBUG: 20:27:06.346: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 218s ** (umockdev-run:4538): DEBUG: 20:27:06.349: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.BNT712/dev/bus/usb/001/001 218s ** (umockdev-run:4538): DEBUG: 20:27:06.349: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 218s ** (umockdev-run:4538): DEBUG: 20:27:06.349: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 218s (process:4542): libfprint-context-DEBUG: 20:27:06.424: Initializing FpContext (libfprint version 1.94.8+tod1) 218s (process:4542): libfprint-tod-DEBUG: 20:27:06.424: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 218s (process:4542): libfprint-context-DEBUG: 20:27:06.427: No driver found for USB device 1D6B:0002 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.427: 186223055: ../libfprint/drivers/synaptics/synaptics.c:1243 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.428: Build Time: 1596608839 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.428: Build Num: 3273255 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.428: Version: 10.1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.428: Target: 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.428: Product: 65 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.428: sequence number is 1 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.428: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.429: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.430: Device reported probe completion 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.430: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 218s (process:4542): libfprint-device-DEBUG: 20:27:06.430: Completing action FPI_DEVICE_ACTION_PROBE in idle! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.430: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.431: 186226978: ../libfprint/drivers/synaptics/synaptics.c:1403 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.431: sequence number is 2 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.431: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.432: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.432: Device reported open completion 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.432: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 218s (process:4542): libfprint-device-DEBUG: 20:27:06.432: Completing action FPI_DEVICE_ACTION_OPEN in idle! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.432: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.432: clear all prints in database 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.432: sequence number is 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.432: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.433: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.433: Deleting All Enrolled Users is 0% complete 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.433: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.434: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.434: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.434: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.434: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.434: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.435: Deleting All Enrolled Users is 100% complete 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.435: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.436: Successfully deleted all enrolled user 218s (process:4542): libfprint-device-DEBUG: 20:27:06.436: Device reported deletion completion 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.436: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 218s (process:4542): libfprint-device-DEBUG: 20:27:06.436: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.436: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.437: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.437: 186232828: ../libfprint/drivers/synaptics/synaptics.c:1014 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.437: user_id: FP1-00000000-0-00000000-nobody, finger: 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.437: sequence number is 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.437: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.437: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.438: Place Finger on the Sensor! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.438: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.438: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.438: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.439: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.439: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.439: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.439: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.439: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.439: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.440: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.440: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.441: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.441: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.441: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.441: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.442: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.442: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.442: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.442: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.443: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.443: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.443: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.443: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.443: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.444: Enrollment is 12 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.444: Device reported enroll progress, reported 1 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.444: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.444: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.445: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.445: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.445: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.446: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.446: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.446: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.447: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.447: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.447: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.447: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.447: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.448: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.448: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.448: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.448: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.448: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.449: Enrollment is 25 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.449: Device reported enroll progress, reported 2 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.449: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.450: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.450: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.450: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.451: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.451: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.451: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.451: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.451: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.451: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.452: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.452: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.453: Enrollment is 37 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.453: Device reported enroll progress, reported 3 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.453: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.453: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.453: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.454: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.454: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.454: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.455: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.455: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.455: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.455: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.455: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.456: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.456: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.456: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.456: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.456: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.456: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.457: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.457: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.458: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.458: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.459: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.459: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.459: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.459: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.459: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.459: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.460: Enrollment is 50 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.460: Device reported enroll progress, reported 4 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.460: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.460: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.461: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.461: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.461: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.462: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.462: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.462: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.463: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.463: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.463: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.463: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.464: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.464: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.464: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.465: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.465: Enrollment is 62 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.465: Device reported enroll progress, reported 5 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.466: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.466: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.466: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.466: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.466: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.467: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.467: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.467: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.467: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.467: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.467: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.468: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.468: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.469: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.469: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.469: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.469: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.469: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.470: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.470: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.470: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.470: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.470: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.471: Enrollment is 62 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.471: Device reported enroll progress, reported 5 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.471: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.471: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.472: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.472: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.472: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.472: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.473: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.473: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.473: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.473: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.473: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.474: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.474: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.474: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.474: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.474: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.475: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.475: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.475: Enrollment is 75 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.475: Device reported enroll progress, reported 6 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.475: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.475: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.475: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.476: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.476: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.476: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.476: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.477: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.477: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.477: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.477: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.477: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.477: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.477: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.478: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.478: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.478: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.478: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.478: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.478: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.479: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.479: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.479: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.479: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.479: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.480: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.480: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.480: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.480: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.480: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.480: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.480: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.480: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.481: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.481: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.481: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.481: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.481: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.481: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.482: Enrollment is 87 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.482: Device reported enroll progress, reported 7 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.482: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.482: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.482: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.483: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.483: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.483: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.483: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.483: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.483: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.483: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.484: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.484: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.484: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.484: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.484: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.484: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.484: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.485: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.485: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.485: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.485: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.485: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.486: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.486: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.486: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.486: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.486: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.486: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.487: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.487: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.487: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.487: Enrollment is 100 % 218s (process:4542): libfprint-device-DEBUG: 20:27:06.487: Device reported enroll progress, reported 8 of 8 have been completed 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.487: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.488: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.488: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.488: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.488: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.488: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.489: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.489: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.489: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.489: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.489: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.489: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.490: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.490: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.490: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.490: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.490: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.490: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.490: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.491: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.491: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.491: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.491: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.491: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.491: Enrollment was successful! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.491: Device reported enroll completion 218s (process:4542): libfprint-device-DEBUG: 20:27:06.491: Device reported finger status change: FP_FINGER_STATUS_NONE 218s (process:4542): libfprint-device-DEBUG: 20:27:06.491: Print for finger FP_FINGER_UNKNOWN enrolled 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.491: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 218s (process:4542): libfprint-device-DEBUG: 20:27:06.491: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.491: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.492: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.492: data is 0x3e6594c0 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.492: 186287745: ../libfprint/drivers/synaptics/synaptics.c:646 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.492: sequence number is 5 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.492: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.492: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.492: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.493: Place Finger on the Sensor! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.493: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.493: got suspend request 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.493: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.493: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.494: got resume request 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.494: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.494: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.494: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.495: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.495: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.495: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.495: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.496: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.496: Finger is now on the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.496: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.496: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.497: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.497: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.497: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.497: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.497: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.498: Fingerprint image capture complete! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.498: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.498: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.498: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.499: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.499: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.499: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-device-DEBUG: 20:27:06.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.499: Finger is now off the sensor 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.499: Received message with 0 sequence number 0x91, ignoring! 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.499: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.500: interrupt transfer done 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.500: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.500: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.501: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.501: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.501: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 218s (process:4542): libfprint-device-DEBUG: 20:27:06.501: Device reported verify result 218s (process:4542): libfprint-device-DEBUG: 20:27:06.501: Device reported verify completion 218s (process:4542): libfprint-device-DEBUG: 20:27:06.501: Device reported finger status change: FP_FINGER_STATUS_NONE 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.501: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 218s (process:4542): libfprint-device-DEBUG: 20:27:06.501: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.501: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.501: data is 0x3e6594c0 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.501: 186297333: ../libfprint/drivers/synaptics/synaptics.c:1123 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.501: sequence number is 6 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.501: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.502: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.502: Successfully deleted enrolled user 218s (process:4542): libfprint-device-DEBUG: 20:27:06.502: Device reported deletion completion 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.502: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 218s (process:4542): libfprint-device-DEBUG: 20:27:06.502: Completing action FPI_DEVICE_ACTION_DELETE in idle! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.502: Not updating temperature model, device can run continuously! 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.502: 186298382: ../libfprint/drivers/synaptics/synaptics.c:1424 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.502: sequence number is 7 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.502: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.503: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 218s (process:4542): libfprint-synaptics-DEBUG: 20:27:06.503: Fingerprint sensor ready to be powered down 218s (process:4542): libfprint-device-DEBUG: 20:27:06.503: Device reported close completion 218s (process:4542): libfprint-SSM-DEBUG: 20:27:06.504: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 218s (process:4542): libfprint-device-DEBUG: 20:27:06.504: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 218s (process:4542): libfprint-device-DEBUG: 20:27:06.504: Not updating temperature model, device can run continuously! 218s enrolling 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 1, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 2, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 3, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 4, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 5, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 6, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 7, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x7bd20bbe8d80 (FpiDeviceSynaptics at 0x3e556d20)>, 8, None, None, None) 218s enroll done 218s verifying 218s verify done 218s deleting 218s delete done 218s libusb: warning [libusb_exit] device 1.1 still referenced 218s ** (umockdev-run:4538): DEBUG: 20:27:06.517: umockdev.vala:154: Removing test bed /tmp/umockdev.BNT712 218s (umockdev-run:4538): GLib-DEBUG: 20:27:06.522: unsetenv() is not thread-safe and should not be used after threads are created 218s PASS: libfprint-2/driver-synaptics.test 218s Running test: libfprint-2/driver-fpcmoc.test 218s ** (umockdev-run:4550): DEBUG: 20:27:06.562: umockdev.vala:127: Created udev test bed /tmp/umockdev.5TIB22 218s ** (umockdev-run:4550): DEBUG: 20:27:06.563: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 218s ** (umockdev-run:4550): DEBUG: 20:27:06.564: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 218s ** (umockdev-run:4550): DEBUG: 20:27:06.567: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5TIB22/dev/bus/usb/001/019 218s ** (umockdev-run:4550): DEBUG: 20:27:06.567: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 218s ** (umockdev-run:4550): DEBUG: 20:27:06.568: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 218s ** (umockdev-run:4550): DEBUG: 20:27:06.571: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5TIB22/dev/bus/usb/001/001 218s ** (umockdev-run:4550): DEBUG: 20:27:06.571: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 218s ** (umockdev-run:4550): DEBUG: 20:27:06.572: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 218s (process:4554): libfprint-context-DEBUG: 20:27:06.646: Initializing FpContext (libfprint version 1.94.8+tod1) 218s (process:4554): libfprint-tod-DEBUG: 20:27:06.646: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 218s (process:4554): libfprint-DEBUG: 20:27:06.648: fpi_device_fpcmoc_init enter --> 218s (process:4554): libfprint-DEBUG: 20:27:06.648: 186443846: ../libfprint/drivers/fpcmoc/fpc.c:1873 218s (process:4554): libfprint-context-DEBUG: 20:27:06.648: No driver found for USB device 1D6B:0002 218s (process:4554): libfprint-DEBUG: 20:27:06.648: fpc_dev_probe enter --> 218s (process:4554): libfprint-DEBUG: 20:27:06.650: Device name: FPC L:0001 FW:127010 218s (process:4554): libfprint-device-DEBUG: 20:27:06.651: Device reported probe completion 218s (process:4554): libfprint-device-DEBUG: 20:27:06.651: Completing action FPI_DEVICE_ACTION_PROBE in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.651: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.652: fpc_dev_open enter --> 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.652: [fpcmoc] FP_INIT_NUM_STATES entering state 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.652: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.652: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-DEBUG: 20:27:06.653: fpc_cmd_receive_cb current ssm request: 1 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.653: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.653: fpc_cmd_receive_cb current ssm request: 1 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.653: fpc_cmd_receive_cb recv evt data length: 38 218s (process:4554): libfprint-DEBUG: 20:27:06.653: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 218s (process:4554): libfprint-DEBUG: 20:27:06.653: fpc_evt_cb INIT: FW version: 1.27.0.10 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.653: [fpcmoc] FP_INIT_NUM_STATES entering state 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.653: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.653: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.654: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.654: fpc_cmd_receive_cb current ssm request: 96 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.654: fpc_init_load_db_cb got dbid size: 16 218s (process:4554): libfprint-DEBUG: 20:27:06.654: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.654: [fpcmoc] FP_INIT_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.654: Device reported open completion 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.654: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.654: Completing action FPI_DEVICE_ACTION_OPEN in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.654: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.654: fpc_dev_clear_storage enter --> 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.654: [fpcmoc] Clear storage entering state 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.654: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.654: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.654: fpc_cmd_receive_cb current ssm request: 98 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.654: [fpcmoc] Clear storage entering state 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.654: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.654: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.655: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.655: fpc_cmd_receive_cb current ssm request: 96 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.655: [fpcmoc] Clear storage completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.655: Clear Storage complete! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.655: Device reported deletion completion 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.655: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.655: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.655: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.655: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.655: fpc_dev_enroll enter --> 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.656: [fpcmoc] enroll entering state 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.656: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.656: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-DEBUG: 20:27:06.656: fpc_cmd_receive_cb current ssm request: 112 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.656: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.657: fpc_cmd_receive_cb current ssm request: 112 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.657: fpc_cmd_receive_cb recv evt data length: 790 218s (process:4554): libfprint-DEBUG: 20:27:06.657: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.657: [fpcmoc] enroll entering state 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.657: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.657: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.657: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.657: fpc_cmd_receive_cb current ssm request: 103 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.657: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-device-DEBUG: 20:27:06.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.657: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.657: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.657: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.658: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.658: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.658: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.658: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.658: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.658: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.658: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.658: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.658: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.659: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.659: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.659: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.659: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.659: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.659: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.659: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.659: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.659: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.659: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.660: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.660: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.660: Enrol Update status: 1, remaining: 11 218s (process:4554): libfprint-device-DEBUG: 20:27:06.660: Device reported enroll progress, reported 1 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.660: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.660: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.660: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.660: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.660: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.660: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.661: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.661: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.661: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.661: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.661: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.661: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.661: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.661: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.662: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.662: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.662: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.662: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.662: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.662: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.662: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.662: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.662: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.662: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.663: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.663: Enrol Update status: 1, remaining: 10 218s (process:4554): libfprint-device-DEBUG: 20:27:06.663: Device reported enroll progress, reported 2 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.663: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.663: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.663: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.663: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.663: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.663: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.664: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.664: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.664: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.664: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.664: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.664: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.664: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.664: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.664: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.665: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.665: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.665: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.665: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.665: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.665: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.665: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.665: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.665: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.665: Enrol Update status: 1, remaining: 9 218s (process:4554): libfprint-device-DEBUG: 20:27:06.665: Device reported enroll progress, reported 3 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.665: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.665: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.665: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.666: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.666: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.666: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.666: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.666: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.666: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.666: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.666: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.667: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.667: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.667: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.667: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.667: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.667: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.667: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.667: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.667: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.667: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.667: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.667: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.668: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.668: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.668: Enrol Update status: 1, remaining: 8 218s (process:4554): libfprint-device-DEBUG: 20:27:06.668: Device reported enroll progress, reported 4 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.668: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.668: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.668: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.668: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.669: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.669: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.669: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.670: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.670: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.670: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.670: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.670: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.670: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.670: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.670: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.670: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.671: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.671: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.671: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.671: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.671: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.671: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.671: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.671: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.671: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.671: Enrol Update status: 1, remaining: 7 218s (process:4554): libfprint-device-DEBUG: 20:27:06.671: Device reported enroll progress, reported 5 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.671: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.671: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.671: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.672: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.672: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.672: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.672: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.672: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.672: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.672: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.672: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.672: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.672: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.673: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.673: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.673: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.673: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.673: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.673: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.673: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.673: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.673: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.673: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.674: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.674: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.674: Enrol Update status: 5, remaining: 7 218s (process:4554): libfprint-DEBUG: 20:27:06.674: Sample overlapping ratio is too High 218s (process:4554): libfprint-device-DEBUG: 20:27:06.674: Device reported enroll progress, reported 5 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.674: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.674: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.674: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.674: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.674: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.674: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.675: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.675: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.675: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.675: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.675: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.675: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.675: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.675: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.675: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.676: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.676: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.676: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.676: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.676: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.676: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.676: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.676: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.676: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.676: Enrol Update status: 1, remaining: 6 218s (process:4554): libfprint-device-DEBUG: 20:27:06.676: Device reported enroll progress, reported 6 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.676: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.676: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.676: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.677: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.677: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.677: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.677: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.677: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.677: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.677: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.677: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.677: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.678: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.678: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.678: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.678: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.678: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.678: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.678: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.678: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.678: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.678: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.679: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.679: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.679: Enrol Update status: 1, remaining: 5 218s (process:4554): libfprint-device-DEBUG: 20:27:06.679: Device reported enroll progress, reported 7 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.679: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.679: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.679: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.679: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.679: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.679: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.680: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.680: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.680: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.680: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.680: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.680: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.680: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.680: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.680: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.680: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.681: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.681: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.681: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.681: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.681: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.681: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.681: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.681: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.681: Enrol Update status: 5, remaining: 5 218s (process:4554): libfprint-DEBUG: 20:27:06.681: Sample overlapping ratio is too High 218s (process:4554): libfprint-device-DEBUG: 20:27:06.681: Device reported enroll progress, reported 7 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.681: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.681: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.681: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.682: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.682: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.682: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.682: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.682: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.682: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.682: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.682: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.682: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.682: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.683: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.683: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.683: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.683: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.683: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.683: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.683: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.683: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.683: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.683: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.684: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.684: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.684: Enrol Update status: 1, remaining: 4 218s (process:4554): libfprint-device-DEBUG: 20:27:06.684: Device reported enroll progress, reported 8 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.684: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.684: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.684: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.684: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.684: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.684: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.685: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.685: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.685: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.685: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.685: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.685: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.685: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.685: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.686: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.686: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.686: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.686: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.686: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.686: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.686: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.686: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.686: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.686: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.687: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.687: Enrol Update status: 1, remaining: 3 218s (process:4554): libfprint-device-DEBUG: 20:27:06.687: Device reported enroll progress, reported 9 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.687: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.687: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.687: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.687: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.687: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.687: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.688: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.688: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.688: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.688: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.688: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.688: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.688: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.688: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.688: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.688: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.689: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.689: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.689: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.689: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.689: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.689: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.689: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.689: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.689: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.689: Enrol Update status: 1, remaining: 2 218s (process:4554): libfprint-device-DEBUG: 20:27:06.689: Device reported enroll progress, reported 10 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.689: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.689: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.689: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.690: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.690: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.690: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.690: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.690: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.690: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.690: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.690: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.690: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.690: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.691: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.691: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.691: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.691: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.691: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.691: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.691: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.691: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.691: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.691: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.692: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.692: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.692: Enrol Update status: 5, remaining: 2 218s (process:4554): libfprint-DEBUG: 20:27:06.692: Sample overlapping ratio is too High 218s (process:4554): libfprint-device-DEBUG: 20:27:06.692: Device reported enroll progress, reported 10 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.692: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.692: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.692: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.692: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.692: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.692: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.693: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.693: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.693: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.693: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.693: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.693: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.693: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.693: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.693: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.693: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.694: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.694: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.694: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.694: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.694: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.694: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.694: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.694: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.694: Enrol Update status: 1, remaining: 1 218s (process:4554): libfprint-device-DEBUG: 20:27:06.694: Device reported enroll progress, reported 11 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.694: [fpcmoc] enroll entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.694: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.694: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.694: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.695: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.695: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.695: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.695: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.695: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.695: [fpcmoc] enroll entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.695: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.695: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.696: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.696: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.696: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.696: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.696: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.696: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.696: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.696: [fpcmoc] enroll entering state 4 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.696: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.696: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.697: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.697: fpc_cmd_receive_cb current ssm request: 104 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.697: Enrol Update status: 0, remaining: 0 218s (process:4554): libfprint-device-DEBUG: 20:27:06.697: Device reported enroll progress, reported 12 of 25 have been completed 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.697: [fpcmoc] enroll entering state 5 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.697: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.697: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.697: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.697: fpc_cmd_receive_cb current ssm request: 105 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.697: Enrol End status: 0, fid: 0x0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.697: [fpcmoc] enroll entering state 6 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.697: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.697: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.698: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.698: fpc_cmd_receive_cb current ssm request: 107 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.698: [fpcmoc] enroll entering state 7 218s (process:4554): libfprint-DEBUG: 20:27:06.698: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.698: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.698: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.698: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.698: fpc_cmd_receive_cb current ssm request: 106 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.698: [fpcmoc] enroll entering state 8 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.698: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.698: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.699: fpc_cmd_receive_cb current ssm request: 97 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] enroll entering state 9 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.699: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.699: fpc_cmd_receive_cb current ssm request: 3 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.699: fpc_do_abort_cb Do abort for reasons 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] enroll entering state 10 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] enroll completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.699: Enrollment complete! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.699: Device reported enroll completion 218s (process:4554): libfprint-device-DEBUG: 20:27:06.699: Device reported finger status change: FP_FINGER_STATUS_NONE 218s (process:4554): libfprint-device-DEBUG: 20:27:06.699: Print for finger FP_FINGER_UNKNOWN enrolled 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.699: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.699: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.699: fpc_dev_template_list enter --> 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.699: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.699: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-DEBUG: 20:27:06.700: fpc_cmd_receive_cb current ssm request: 112 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.700: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.700: fpc_cmd_receive_cb current ssm request: 112 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.700: fpc_cmd_receive_cb recv evt data length: 790 218s (process:4554): libfprint-DEBUG: 20:27:06.701: Query templates complete! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.701: Device reported listing completion 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.701: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.701: Completing action FPI_DEVICE_ACTION_LIST in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.701: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.701: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.701: fpc_dev_verify_identify enter --> 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.701: [fpcmoc] verify_identify entering state 0 218s (process:4554): libfprint-device-DEBUG: 20:27:06.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.701: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.701: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-DEBUG: 20:27:06.701: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.701: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.702: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.702: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.702: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.702: [fpcmoc] verify_identify entering state 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.702: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.702: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.702: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.702: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.702: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.703: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.703: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.703: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.703: [fpcmoc] verify_identify entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.703: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.703: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.703: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.703: fpc_cmd_receive_cb current ssm request: 107 state: 0 218s (process:4554): libfprint-device-DEBUG: 20:27:06.703: Device reported verify result 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.703: [fpcmoc] verify_identify entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.703: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.703: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.704: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.704: fpc_cmd_receive_cb current ssm request: 3 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.704: fpc_do_abort_cb Do abort for reasons 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.704: [fpcmoc] verify_identify completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.704: Verify_identify complete! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.704: Device reported verify completion 218s (process:4554): libfprint-device-DEBUG: 20:27:06.704: Device reported finger status change: FP_FINGER_STATUS_NONE 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.704: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.704: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.704: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.704: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.704: fpc_dev_verify_identify enter --> 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.704: [fpcmoc] verify_identify entering state 0 218s (process:4554): libfprint-device-DEBUG: 20:27:06.704: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.704: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.704: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 218s (process:4554): libfprint-DEBUG: 20:27:06.705: fpc_cmd_receive_cb current ssm request: 2 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.705: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.705: fpc_cmd_receive_cb current ssm request: 2 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.705: fpc_cmd_receive_cb recv evt data length: 12 218s (process:4554): libfprint-DEBUG: 20:27:06.705: fpc_evt_cb Got finger down event (0) 218s (process:4554): libfprint-device-DEBUG: 20:27:06.705: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.705: [fpcmoc] verify_identify entering state 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.705: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.705: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.706: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.706: fpc_cmd_receive_cb current ssm request: 9 state: 0 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.706: [fpcmoc] FP_CMD_NUM_STATES entering state 1 218s (process:4554): libfprint-DEBUG: 20:27:06.706: fpc_cmd_receive_cb current ssm request: 9 state: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.706: fpc_cmd_receive_cb recv evt data length: 24 218s (process:4554): libfprint-DEBUG: 20:27:06.706: fpc_evt_cb Got capture event 218s (process:4554): libfprint-device-DEBUG: 20:27:06.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.706: [fpcmoc] verify_identify entering state 2 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.706: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.706: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.706: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.707: fpc_cmd_receive_cb current ssm request: 107 state: 0 218s (process:4554): libfprint-device-DEBUG: 20:27:06.707: Device reported identify result 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.707: [fpcmoc] verify_identify entering state 3 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.707: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.707: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.707: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.707: fpc_cmd_receive_cb current ssm request: 3 state: 0 218s (process:4554): libfprint-DEBUG: 20:27:06.707: fpc_do_abort_cb Do abort for reasons 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.707: [fpcmoc] verify_identify completed successfully 218s (process:4554): libfprint-DEBUG: 20:27:06.707: Verify_identify complete! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.707: Device reported identify completion 218s (process:4554): libfprint-device-DEBUG: 20:27:06.707: Device reported finger status change: FP_FINGER_STATUS_NONE 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.707: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.707: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.707: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.708: fpc_dev_template_delete enter --> 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.708: [fpcmoc] FP_CMD_NUM_STATES entering state 0 218s (process:4554): libfprint-DEBUG: 20:27:06.708: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 218s (process:4554): libfprint-DEBUG: 20:27:06.708: fpc_dev_template_delete exit <-- 218s (process:4554): libfprint-DEBUG: 20:27:06.708: fpc_cmd_receive_cb current ssm request: 99 state: 0 218s (process:4554): libfprint-device-DEBUG: 20:27:06.708: Device reported deletion completion 218s (process:4554): libfprint-SSM-DEBUG: 20:27:06.708: [fpcmoc] FP_CMD_NUM_STATES completed successfully 218s (process:4554): libfprint-device-DEBUG: 20:27:06.708: Completing action FPI_DEVICE_ACTION_DELETE in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.708: Not updating temperature model, device can run continuously! 218s (process:4554): libfprint-DEBUG: 20:27:06.708: fpc_dev_close enter --> 218s (process:4554): libfprint-device-DEBUG: 20:27:06.709: Device reported close completion 218s (process:4554): libfprint-device-DEBUG: 20:27:06.709: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 218s (process:4554): libfprint-device-DEBUG: 20:27:06.709: Not updating temperature model, device can run continuously! 218s Clear 218s Clear done 218s enrolling 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 1, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 2, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 3, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 4, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 5, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 6, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 7, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 8, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 9, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 10, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 11, None, None, None) 218s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0x78d3a4315e80 (FpiDeviceFpcMoc at 0x12612e50)>, 12, None, None, None) 218s enroll done 218s listing 218s listing done 218s verifying 218s verify done 218s async identifying 218s indentification_done: 218s deleting 218s delete done 218s ** (umockdev-run:4550): DEBUG: 20:27:06.721: umockdev.vala:154: Removing test bed /tmp/umockdev.5TIB22 218s (umockdev-run:4550): GLib-DEBUG: 20:27:06.727: unsetenv() is not thread-safe and should not be used after threads are created 218s PASS: libfprint-2/driver-fpcmoc.test 218s Running test: libfprint-2/driver-vfs301.test 218s ** (umockdev-run:4562): DEBUG: 20:27:06.766: umockdev.vala:127: Created udev test bed /tmp/umockdev.V9LF22 218s ** (umockdev-run:4562): DEBUG: 20:27:06.766: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 218s ** (umockdev-run:4562): DEBUG: 20:27:06.767: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 218s ** (umockdev-run:4562): DEBUG: 20:27:06.771: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.V9LF22/dev/bus/usb/002/005 218s ** (umockdev-run:4562): DEBUG: 20:27:06.771: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 218s ** (umockdev-run:4562): DEBUG: 20:27:06.771: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 218s ** (umockdev-run:4562): DEBUG: 20:27:06.774: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.V9LF22/dev/bus/usb/002/002 218s ** (umockdev-run:4562): DEBUG: 20:27:06.774: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 218s ** (umockdev-run:4562): DEBUG: 20:27:06.775: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 218s ** (umockdev-run:4562): DEBUG: 20:27:06.778: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.V9LF22/dev/bus/usb/002/001 218s ** (umockdev-run:4562): DEBUG: 20:27:06.778: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0 218s ** (umockdev-run:4562): DEBUG: 20:27:06.778: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 218s (umockdev-run:4562): GLib-GIO-DEBUG: 20:27:06.780: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 218s (process:4566): libfprint-context-DEBUG: 20:27:06.867: Initializing FpContext (libfprint version 1.94.8+tod1) 218s (process:4566): libfprint-tod-DEBUG: 20:27:06.868: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 218s (process:4566): libfprint-context-DEBUG: 20:27:06.870: No driver found for USB device 8087:0020 218s (process:4566): libfprint-context-DEBUG: 20:27:06.870: No driver found for USB device 1D6B:0002 218s (process:4566): libfprint-device-DEBUG: 20:27:06.870: Device reported probe completion 218s (process:4566): libfprint-device-DEBUG: 20:27:06.870: Completing action FPI_DEVICE_ACTION_PROBE in idle! 218s (process:4566): libfprint-device-DEBUG: 20:27:06.870: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 218s (process:4566): libfprint-image_device-DEBUG: 20:27:06.871: Image device open completed 218s (process:4566): libfprint-device-DEBUG: 20:27:06.871: Device reported open completion 218s (process:4566): libfprint-device-DEBUG: 20:27:06.871: Completing action FPI_DEVICE_ACTION_OPEN in idle! 218s (process:4566): libfprint-device-DEBUG: 20:27:06.871: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 218s (process:4566): libfprint-device-DEBUG: 20:27:06.872: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 218s (process:4566): libfprint-image_device-DEBUG: 20:27:06.872: Activating image device 218s (process:4566): libfprint-image_device-DEBUG: 20:27:06.872: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 218s (process:4566): libfprint-SSM-DEBUG: 20:27:06.872: [vfs301] 1 entering state 0 218s (process:4566): libfprint-SSM-DEBUG: 20:27:06.900: [vfs301] 1 completed successfully 218s (process:4566): libfprint-image_device-DEBUG: 20:27:06.900: Image device activation completed 218s (process:4566): libfprint-image_device-DEBUG: 20:27:06.900: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 218s (process:4566): libfprint-image_device-DEBUG: 20:27:06.900: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 218s (process:4566): libfprint-SSM-DEBUG: 20:27:06.900: [vfs301] M_LOOP_NUM_STATES entering state 0 218s (process:4566): libfprint-SSM-DEBUG: 20:27:06.901: [vfs301] M_LOOP_NUM_STATES entering state 1 218s (process:4566): libfprint-device-DEBUG: 20:27:06.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:4566): libfprint-device-DEBUG: 20:27:06.971: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.101: [vfs301] M_LOOP_NUM_STATES entering state 2 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.101: [vfs301] M_LOOP_NUM_STATES entering state 1 219s Executing: libfprint-2/driver-vfs301.test 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.302: [vfs301] M_LOOP_NUM_STATES entering state 2 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.302: [vfs301] M_LOOP_NUM_STATES entering state 3 219s (process:4566): libfprint-device-DEBUG: 20:27:07.302: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.302: Image device reported finger status: on 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.303: [vfs301] M_LOOP_NUM_STATES entering state 4 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.503: [vfs301] M_LOOP_NUM_STATES entering state 5 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.505: [vfs301] M_LOOP_NUM_STATES entering state 6 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Image device captured an image 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:4566): libfprint-device-DEBUG: 20:27:07.505: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:4566): libfprint-SSM-DEBUG: 20:27:07.505: [vfs301] M_LOOP_NUM_STATES completed successfully 219s (process:4566): libfprint-device-DEBUG: 20:27:07.505: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Image device reported finger status: off 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Deactivating image device 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Image device deactivation completed 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.505: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 219s (process:4566): libfprint-image-DEBUG: 20:27:07.518: Minutiae scan completed in 0.012450 secs 219s (process:4566): libfprint-device-DEBUG: 20:27:07.518: Device reported capture completion 219s (process:4566): libfprint-device-DEBUG: 20:27:07.518: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 219s (process:4566): libfprint-device-DEBUG: 20:27:07.518: Updated temperature model after 0.55 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s (process:4566): libfprint-image_device-DEBUG: 20:27:07.518: Image device close completed 219s (process:4566): libfprint-device-DEBUG: 20:27:07.518: Device reported close completion 219s (process:4566): libfprint-device-DEBUG: 20:27:07.518: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 219s (process:4566): libfprint-device-DEBUG: 20:27:07.518: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s ** (umockdev-run:4562): DEBUG: 20:27:07.577: umockdev.vala:154: Removing test bed /tmp/umockdev.V9LF22 219s (umockdev-run:4562): GLib-DEBUG: 20:27:07.583: unsetenv() is not thread-safe and should not be used after threads are created 219s Comparing PNGs /tmp/libfprint-umockdev-test-xl3w8se4/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 219s PASS: libfprint-2/driver-vfs301.test 219s Running test: libfprint-2/driver-upektc_img.test 219s ** (umockdev-run:4575): DEBUG: 20:27:07.634: umockdev.vala:127: Created udev test bed /tmp/umockdev.Z8RC22 219s ** (umockdev-run:4575): DEBUG: 20:27:07.634: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 219s ** (umockdev-run:4575): DEBUG: 20:27:07.635: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 219s ** (umockdev-run:4575): DEBUG: 20:27:07.638: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z8RC22/dev/bus/usb/001/003 219s ** (umockdev-run:4575): DEBUG: 20:27:07.639: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 219s ** (umockdev-run:4575): DEBUG: 20:27:07.639: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 219s ** (umockdev-run:4575): DEBUG: 20:27:07.642: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z8RC22/dev/bus/usb/001/002 219s ** (umockdev-run:4575): DEBUG: 20:27:07.642: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 219s ** (umockdev-run:4575): DEBUG: 20:27:07.643: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 219s ** (umockdev-run:4575): DEBUG: 20:27:07.646: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z8RC22/dev/bus/usb/001/001 219s ** (umockdev-run:4575): DEBUG: 20:27:07.646: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0 219s ** (umockdev-run:4575): DEBUG: 20:27:07.646: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 219s (process:4579): libfprint-context-DEBUG: 20:27:07.715: Initializing FpContext (libfprint version 1.94.8+tod1) 219s (process:4579): libfprint-tod-DEBUG: 20:27:07.715: Impossible to load the shared drivers dir Error opening directory “/usr/lib/x86_64-linux-gnu/libfprint-2/tod-1”: No such file or directory 219s (process:4579): libfprint-context-DEBUG: 20:27:07.717: No driver found for USB device 8087:0020 219s (process:4579): libfprint-context-DEBUG: 20:27:07.717: No driver found for USB device 1D6B:0002 219s (process:4579): libfprint-device-DEBUG: 20:27:07.717: Device reported probe completion 219s (process:4579): libfprint-device-DEBUG: 20:27:07.717: Completing action FPI_DEVICE_ACTION_PROBE in idle! 219s (process:4579): libfprint-device-DEBUG: 20:27:07.717: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.719: Image device open completed 219s (process:4579): libfprint-device-DEBUG: 20:27:07.719: Device reported open completion 219s (process:4579): libfprint-device-DEBUG: 20:27:07.719: Completing action FPI_DEVICE_ACTION_OPEN in idle! 219s (process:4579): libfprint-device-DEBUG: 20:27:07.719: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 219s (process:4579): libfprint-device-DEBUG: 20:27:07.719: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.719: Activating image device 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.719: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.719: [upektc_img] ACTIVATE_NUM_STATES entering state 0 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.719: [upektc_img] ACTIVATE_NUM_STATES entering state 1 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.720: [upektc_img] ACTIVATE_NUM_STATES entering state 2 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.720: [upektc_img] ACTIVATE_NUM_STATES entering state 3 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.721: [upektc_img] ACTIVATE_NUM_STATES entering state 4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.721: [upektc_img] ACTIVATE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.722: [upektc_img] ACTIVATE_NUM_STATES entering state 6 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.722: [upektc_img] ACTIVATE_NUM_STATES entering state 7 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.722: [upektc_img] ACTIVATE_NUM_STATES entering state 8 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.723: [upektc_img] ACTIVATE_NUM_STATES entering state 9 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.723: [upektc_img] ACTIVATE_NUM_STATES entering state 10 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.724: [upektc_img] ACTIVATE_NUM_STATES entering state 11 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.724: Sensor type : TCS4x, width x height: 192 x 512 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.724: [upektc_img] ACTIVATE_NUM_STATES completed successfully 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.724: Image device activation completed 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.724: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.724: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 219s (process:4579): libfprint-device-DEBUG: 20:27:07.724: Device reported finger status change: FP_FINGER_STATUS_NEEDED 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.724: [upektc_img] CAPTURE_NUM_STATES entering state 0 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.725: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.725: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.725: 18th byte is 0c 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.725: [upektc_img] CAPTURE_NUM_STATES entering state 3 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.726: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.726: request completed, len: 0040 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.726: [upektc_img] CAPTURE_NUM_STATES entering state 4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.727: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.727: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.727: 18th byte is 00 219s (process:4579): libfprint-device-DEBUG: 20:27:07.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.727: [upektc_img] CAPTURE_NUM_STATES entering state 3 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.727: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.728: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.728: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.728: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.728: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.728: request completed, len: 07c4 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.728: Image device reported finger status: on 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.728: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.728: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.729: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.729: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.729: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.729: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.729: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.730: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.730: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.730: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.730: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.730: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.730: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.730: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.731: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.731: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.731: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.732: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.732: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.732: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.732: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.732: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.732: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.732: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.733: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.733: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.733: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.733: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.733: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.733: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.734: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.734: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.734: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.734: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.734: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.735: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.735: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.735: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.735: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.735: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.735: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.735: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.736: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.736: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.736: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.737: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.737: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.737: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.737: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.737: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.737: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.737: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.738: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.738: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.738: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.738: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.738: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.738: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.739: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.739: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.739: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.739: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.739: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.739: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.739: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.740: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.740: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.740: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.740: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.740: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.741: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.741: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.741: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.741: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.741: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.741: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.741: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.742: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.742: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.742: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.743: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.743: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.743: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.743: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.743: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.743: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.743: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.744: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.744: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.744: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.744: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.744: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.744: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.745: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.745: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.745: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.745: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.745: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.745: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.745: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.746: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.746: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.746: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.746: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.746: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.747: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.747: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.747: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.747: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.747: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.747: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.747: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.748: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.748: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.748: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.748: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.748: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.748: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.748: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.749: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.749: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.749: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.750: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.750: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.750: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.750: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.750: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.750: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.751: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.751: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.751: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.751: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.751: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.751: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.751: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.752: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.752: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.752: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.752: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.752: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.752: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.752: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.753: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.753: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.753: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.753: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.753: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.754: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.754: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.754: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.754: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.754: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.754: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.754: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.755: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.755: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.755: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.756: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.756: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.756: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.756: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.756: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.756: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.756: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.757: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.757: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.757: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.757: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.757: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.757: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.758: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.758: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.758: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.758: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.758: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.758: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.758: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.759: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.759: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.759: response_size is 2052, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.759: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.759: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.759: request completed, len: 07c4 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.759: [upektc_img] CAPTURE_NUM_STATES entering state 5 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.760: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.760: request completed, len: 0040 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.760: response_size is 186, actual_length is 64 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.760: Waiting for rest of transfer 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.760: [upektc_img] CAPTURE_NUM_STATES entering state 1 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.760: request completed, len: 007a 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.760: Image size is 55296 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.760: Image device captured an image 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.761: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 219s (process:4579): libfprint-device-DEBUG: 20:27:07.761: Device reported finger status change: FP_FINGER_STATUS_PRESENT 219s (process:4579): libfprint-device-DEBUG: 20:27:07.761: Device reported finger status change: FP_FINGER_STATUS_NONE 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.762: Image device reported finger status: off 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.762: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.762: Deactivating image device 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.762: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.762: [upektc_img] CAPTURE_NUM_STATES completed successfully 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.762: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.762: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 219s (process:4579): libfprint-SSM-DEBUG: 20:27:07.763: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 219s (process:4579): libfprint-upektc_img-DEBUG: 20:27:07.763: Deactivate completed 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.763: Image device deactivation completed 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.763: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 219s (process:4579): libfprint-image-DEBUG: 20:27:07.768: Minutiae scan completed in 0.007315 secs 219s (process:4579): libfprint-device-DEBUG: 20:27:07.768: Device reported capture completion 219s (process:4579): libfprint-device-DEBUG: 20:27:07.768: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 219s (process:4579): libfprint-device-DEBUG: 20:27:07.768: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 219s (process:4579): libfprint-image_device-DEBUG: 20:27:07.768: Image device close completed 219s (process:4579): libfprint-device-DEBUG: 20:27:07.768: Device reported close completion 219s (process:4579): libfprint-device-DEBUG: 20:27:07.768: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 219s (process:4579): libfprint-device-DEBUG: 20:27:07.768: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 219s ** (umockdev-run:4575): DEBUG: 20:27:07.830: umockdev.vala:154: Removing test bed /tmp/umockdev.Z8RC22 219s (umockdev-run:4575): GLib-DEBUG: 20:27:07.837: unsetenv() is not thread-safe and should not be used after threads are created 219s Comparing PNGs /tmp/libfprint-umockdev-test-fcc2l88j/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 219s PASS: libfprint-2/driver-upektc_img.test 219s SUMMARY: total=64; passed=64; skipped=0; failed=0; user=17.4s; system=10.4s; maxrss=47252 220s autopkgtest [20:27:08]: test installed-tests: -----------------------] 221s installed-tests PASS 221s autopkgtest [20:27:09]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 221s autopkgtest [20:27:09]: @@@@@@@@@@@@@@@@@@@@ summary 221s installed-tests PASS 239s nova [W] Skipping flock for amd64 239s Creating nova instance adt-plucky-amd64-libfprint-20250215-202328-juju-7f2275-prod-proposed-migration-environment-2-0ce0d275-9c56-48fa-b4c2-08e2d512ac02 from image adt/ubuntu-plucky-amd64-server-20250215.img (UUID d1f7bb98-7df8-4026-816e-9f6798166d8b)... 239s nova [W] Timed out waiting for c0ee14ad-e346-4d63-a01e-3a5017b3fb9d to get deleted.